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

Поиск
Список
Период
Сортировка
От Eric Ridge
Тема Read Committed Transaction Isolation and SELECT ... UNION ... SELECT
Дата
Msg-id AANLkTimcKGMS1W25q4-Yznqec3AQfL9q+8XSWvkAOD4r@mail.gmail.com
обсуждение исходный текст
Ответы Re: Read Committed Transaction Isolation and SELECT ... UNION ... SELECT  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: fork() and dynamically loaded c functions....
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Read Committed Transaction Isolation and SELECT ... UNION ... SELECT