Read Committed Transaction Isolation and SELECT ... UNION ... SELECT - Mailing list pgsql-general

From Eric Ridge
Subject Read Committed Transaction Isolation and SELECT ... UNION ... SELECT
Date
Msg-id AANLkTimcKGMS1W25q4-Yznqec3AQfL9q+8XSWvkAOD4r@mail.gmail.com
Whole thread Raw
Responses Re: Read Committed Transaction Isolation and SELECT ... UNION ... SELECT
List pgsql-general
I think I've been studying the documentation too long and have thought
myself into a circle.

http://www.postgresql.org/docs/8.4/static/transaction-iso.html says:

"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 get that what that means in normal cases, but what about a single
query comprised of one or more unions:

      SELECT ... FROM foo WHERE ...
            UNION
      SELECT  ... FROM foo WHERE ...

Since the above is one query issued by the client, are the two SELECT
statements still operating within the same snapshot?  Is the above
considered to be one command?

I think the answer to those questions is "Yes", but I'd appreciate
some clarification.

Thanks in advance!

eric

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: fork() and dynamically loaded c functions....
Next
From: Tom Lane
Date:
Subject: Re: Read Committed Transaction Isolation and SELECT ... UNION ... SELECT