determine snapshot after obtaining locks for first statement - Mailing list pgsql-hackers

From Kevin Grittner
Subject determine snapshot after obtaining locks for first statement
Date
Msg-id 4B290861020000250002D644@gw.wicourts.gov
Whole thread Raw
Responses Re: determine snapshot after obtaining locks for first statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Scott Bailey
Date:
Subject: Re: Range types
Next
From: Bruce Momjian
Date:
Subject: Re: Largeobject Access Controls and pg_migrator