Re: Detecting File Damage & Inconsistencies

From: Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(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 06:42:29
Message-ID: CAGRY4nwB07k2Y3CujUQ8p6trw3ywZzHxek53=17tUgpsyiyU5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Li Japin 2020-11-18 06:57:13 Re: Terminate the idle sessions
Previous Message Junfeng Yang 2020-11-18 06:32:51 vac_update_datfrozenxid will raise "wrong tuple length" if pg_database tuple contains toast attribute.