Re: [HACKERS] How to determine that a TransactionId is really aborted?
От | Peter Geoghegan |
---|---|
Тема | Re: [HACKERS] How to determine that a TransactionId is really aborted? |
Дата | |
Msg-id | CAH2-WzmLrNsD2yU66S5g4crdTJ_8njnsO55BA84M9XaK8HGfOA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] How to determine that a TransactionId is reallyaborted? (Eric Ridge <eebbrr@gmail.com>) |
Ответы |
Re: [HACKERS] How to determine that a TransactionId is reallyaborted?
|
Список | pgsql-hackers |
On Sun, Oct 22, 2017 at 2:19 PM, Eric Ridge <eebbrr@gmail.com> wrote: > I'm looking for the status as any concurrent open transaction might see it. For example, if any concurrent transactionmight see it as "in progress", that's what I'd want returned. Does that make sense? Maybe, but note that that's fundamentally something that can become stale immediately. And, just because an MVCC snapshot cannot see a row does not mean that it cannot affect its transaction/statement in some other way (e.g. unique index enforcement). Again, you'll probably need to put this low level requirement into context if you want sound advice from this list. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: