Does optimizer take into account updates made during same transaction?

Hypothetical macro example:

REPLACE MACRO DERIVE_TRG(
DELETE FROM TRG;
-- For following insert, optimizer correctly estimates,
-- that approx. 6 million rows will be inserted.
INSERT INTO TRG SELECT .. FROM SRC_A;
-- How much rows does optimizer thinks
-- there are in TRG at this point?
UPDATE TRG FROM SRC_B SET a=b WHERE ...;
);

Is there a way of forcing optimizer to use estimate from previous statement?