AK <alk...@gmail.com> wrote: > The following is not precise: > > 13.2.1. Read Committed Isolation Level > > "Also note that two successive SELECT commands can see different data, even > though they are within a single transaction, if other transactions commit > changes during execution of the first SELECT." > > I think it should be re-worded as follows > > "Also note that two successive SELECT commands can see different data, even > though they are within a single transaction, if other transactions commit > after the first SELECT starts, and before the second SELECT starts." > > The reason: there could be other DML running between these two SELECTs.
That's a fair point. I'll commit something to the master branch. I don't think this rises to the level of a documentation bug that needs to be back-patched. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
