| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Eric Ridge <eebbrr(at)gmail(dot)com> |
| Cc: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How to determine that a TransactionId is really aborted? |
| Date: | 2017-10-22 21:24:26 |
| Message-ID: | CAH2-WzmLrNsD2yU66S5g4crdTJ_8njnsO55BA84M9XaK8HGfOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 22, 2017 at 2:19 PM, Eric Ridge <eebbrr(at)gmail(dot)com> wrote:
> I'm looking for the status as any concurrent open transaction might see it. For example, if any concurrent transaction might 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric Ridge | 2017-10-22 21:44:12 | Re: How to determine that a TransactionId is really aborted? |
| Previous Message | Eric Ridge | 2017-10-22 21:19:58 | Re: How to determine that a TransactionId is really aborted? |