Re: [HACKERS] How to determine that a TransactionId is really aborted? - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [HACKERS] How to determine that a TransactionId is really aborted?
Date
Msg-id CAH2-WzmLrNsD2yU66S5g4crdTJ_8njnsO55BA84M9XaK8HGfOA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] How to determine that a TransactionId is reallyaborted?  (Eric Ridge <eebbrr@gmail.com>)
Responses Re: [HACKERS] How to determine that a TransactionId is reallyaborted?
List 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 by date:

Previous
From: Eric Ridge
Date:
Subject: Re: [HACKERS] How to determine that a TransactionId is reallyaborted?
Next
From: Eric Ridge
Date:
Subject: Re: [HACKERS] How to determine that a TransactionId is reallyaborted?