From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com> |
Cc: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Detecting File Damage & Inconsistencies |
Date: | 2020-11-18 10:23:41 |
Message-ID: | CANP8+jLmBGxwnSnc-5gVoMqaJyF8XMc5b_gLGApy8SEwrWFONg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 18 Nov 2020 at 06:42, Craig Ringer
<craig(dot)ringer(at)enterprisedb(dot)com> wrote:
>
> On Fri, Nov 13, 2020 at 7:24 PM Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>
>>
>> What I'm proposing is an option to add 16 bytes onto each COMMIT
>> record
>
>
> Would it make sense to write this at the time we write a topxid assignment to WAL instead?
>
> Otherwise it won't be accessible to streaming-mode logical decoding.
Do you mean extend the xl_xact_assignment record? My understanding is
that is not sent in all cases, so not sure what you mean by "instead".
--
Simon Riggs http://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2020-11-18 10:27:54 | Re: VACUUM (DISABLE_PAGE_SKIPPING on) |
Previous Message | vignesh C | 2020-11-18 10:14:33 | Re: Parallel copy |