Re: Re: any way for a transaction to "see" inserts done earlier in the transaction?
| От | Susan Cassidy |
|---|---|
| Тема | Re: Re: any way for a transaction to "see" inserts done earlier in the transaction? |
| Дата | |
| Msg-id | CAE3Q8okMDh5mE+nkKNZ_iC56+N-z+oq7Fy2p35RYALe+DK0-+A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Re: any way for a transaction to "see" inserts done earlier in the transaction? (Alban Hertroys <haramrae@gmail.com>) |
| Список | pgsql-general |
I suppose it's possible. I've never seen this behavior before, but I don't think I've ever used this same scenario before. It is slightly unusual.
Susan
Susan
On Wed, Apr 16, 2014 at 11:55 PM, Alban Hertroys <haramrae@gmail.com> wrote:
On 17 Apr 2014, at 2:49, David G Johnston <david.g.johnston@gmail.com> wrote:
> Robert DiFalco wrote
>> Two common cases I can think of:
>>
>> 1. The PERL framework is only caching the insert and does not actually
>> perform it until commit is issued.
>
> Wouldn't the same mechanism cache the corresponding SELECT?
Not likely, or if it did it wouldn’t be able to know what id was returned from the function (which calls nextval(), but that isn’t relevant here since it’s marked volatile).
That makes it a possible scenario for what’s being witnessed here.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: