determine snapshot after obtaining locks for first statement

The Cahill thesis mentions an interesting optimization -- they defer
determination of the snapshot until after any locks required for the
first statement have been acquired.  Where the first statement was,
for example, an UPDATE, this reduced re-reads or rollbacks in the
face of concurrent modifications.
Does PostgreSQL currently do this?  If not, would it make sense?
-Kevin