Re: Sketch of a fix for that truncation data corruption issue - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Sketch of a fix for that truncation data corruption issue
Date
Msg-id 20181211213341.6osh3n5pwcugt5am@alap3.anarazel.de
Whole thread Raw
In response to Sketch of a fix for that truncation data corruption issue  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Sketch of a fix for that truncation data corruption issue  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Hi,

On 2018-12-10 15:38:55 -0500, Tom Lane wrote:
> Also, I'm not entirely sure whether there's anything in our various
> replication logic that's dependent on vacuum truncation taking AEL.
> Offhand I'd expect the reduced use of AEL to be a plus, but maybe
> I'm missing something.

It'd be a *MAJOR* plus.  One of the biggest operational headaches for
using a HS node for querying is that there'll often be conflicts due to
vacuum truncating relations (which logs an AEL), even if
hot_standby_feedback is used.  There's been multiple proposals to
allow disabling truncations just because of that.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Sketch of a fix for that truncation data corruption issue
Next
From: David Steele
Date:
Subject: Re: Remove Deprecated Exclusive Backup Mode