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

From Stephen Frost
Subject Re: Sketch of a fix for that truncation data corruption issue
Date
Msg-id 20190105190127.GP2528@tamriel.snowman.net
Whole thread Raw
In response to Re: Sketch of a fix for that truncation data corruption issue  (Andres Freund <andres@anarazel.de>)
Responses Re: Sketch of a fix for that truncation data corruption issue  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-hackers
Greetings,

* Andres Freund (andres@anarazel.de) wrote:
> 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.

Huge +1 from me here, we've seen this too.  Getting rid of the conflict
when using a HS node for querying would be fantastic.

Thanks!

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: ALTER INDEX fails on partitioned index
Next
From: Stephen Frost
Date:
Subject: Re: Why not represent "never vacuumed" accurately wrtpg_class.relpages?