From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [bugfix] commit timestamps ERROR on lookup of FrozenTransactionId |
Date: | 2016-11-23 13:02:31 |
Message-ID: | CAMsr+YHiV7Cean8b_z2+hNZziyn-afbEyc9AFFKU5WGUjcJvzQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 23 November 2016 at 20:58, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> Hi all
>
> Today I ran into an issue where commit timestamp lookups were failing with
>
> ERROR: cannot retrieve commit timestamp for transaction 2
>
> which is of course FrozenTransactionId.
>
> TransactionIdGetCommitTsData(...) ERRORs on !TransactionIdIsNormal(),
> which I think is wrong. Attached is a patch to make it return 0 for
> FrozenTransactionId and BootstrapTransactionId, like it does for xids
> that are too old.
>
> Note that the prior behaviour was as designed and has tests to enforce
> it. I just think it's wrong, and it's also not documented.
>
> IMO this should be back-patched to 9.6 and, without the TAP test part, to 9.5.
Updated to correct the other expected file, since there's an alternate.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0001-Treat-frozen-and-bootstrap-xids-as-old-not-invalid-f.patch | text/x-patch | 4.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-11-23 13:37:38 | Re: Logical decoding on standby |
Previous Message | Craig Ringer | 2016-11-23 12:58:22 | [bugfix] commit timestamps ERROR on lookup of FrozenTransactionId |