Postgres Pro
Downloads
Home   >   mailing lists

Re: Detecting File Damage & Inconsistencies - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Detecting File Damage & Inconsistencies
Date
Msg-id CAGRY4nwB07k2Y3CujUQ8p6trw3ywZzHxek53=17tUgpsyiyU5g@mail.gmail.com
Whole thread Raw
In response to Re: Detecting File Damage & Inconsistencies  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Detecting File Damage & Inconsistencies  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Tree view
On Fri, Nov 13, 2020 at 7:24 PM Simon Riggs <simon@2ndquadrant.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.

pgsql-hackers by date:

Previous
From: Junfeng Yang
Date:
Subject: vac_update_datfrozenxid will raise "wrong tuple length" if pg_database tuple contains toast attribute.
Next
From: Li Japin
Date:
Subject: Re: Terminate the idle sessions