| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Álvaro Herrera <alvaro(dot)herrera(at)2ndquadrant(dot)com> |
| Subject: | Re: [PATCH] Transaction traceability - txid_status(bigint) |
| Date: | 2017-03-22 03:35:12 |
| Message-ID: | CAMsr+YHUzD8mfp8Ly_pNjuTEVcy+mXGkADfpUFh9t=-FEqaq=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22 March 2017 at 09:49, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>> Overall, though, I think that 0001 looks far better than any previous
>> iteration. It's simple. It looks safe. It seems unlikely to break
>> anything that works now. Woo hoo!
>
> Funny that this started with "hey, here's a simple, non-invasive
> function for looking up the status of an arbitrary xid".
Changes made per discussion.
Removed the comments on TransactionIdDidCommit and
TransactionIdDidAbort . It's not going to be relevant for the immense
majority of callers anyway, and callers that are looking up arbitrary
user supplied XIDs will (hopefully) be looking at
TransactionIdInRecentPast anyway.
I'll be leaving the 'xid' vs 'bigint' issues elsewhere in Pg for next
release, nowhere near time for that now.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-race-between-clog-truncation-and-lookup.patch | text/x-patch | 14.0 KB |
| 0002-Introduce-txid_status-bigint-to-get-status-of-an-xac.patch | text/x-patch | 12.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-03-22 03:39:32 | Re: Allow pg_dumpall to work without pg_authid |
| Previous Message | Tom Lane | 2017-03-22 03:34:49 | Re: Allow pg_dumpall to work without pg_authid |