Read Committed Transaction Isolation and SELECT ... UNION ... SELECT

From: Eric Ridge <eebbrr(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Read Committed Transaction Isolation and SELECT ... UNION ... SELECT
Date: 2010-08-10 22:24:39
Message-ID: AANLkTimcKGMS1W25q4-Yznqec3AQfL9q+8XSWvkAOD4r@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-08-10 22:46:49 Re: Read Committed Transaction Isolation and SELECT ... UNION ... SELECT
Previous Message Tom Lane 2010-08-10 21:57:47 Re: fork() and dynamically loaded c functions....