Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE. - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.
Date
Msg-id 20160415201957.axg47zfktng53wzx@alap3.anarazel.de
Whole thread Raw
In response to Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2016-04-15 15:26:17 -0400, Tom Lane wrote:
> I think the bottom line is that we misdesigned the WAL representation
> by assuming that this sort of info could always be piggybacked on a
> transaction commit record.  It's time to fix that.

I think we got to piggyback it onto a commit record, as long as there's
one. Otherwise it's going to be more complex (queuing messages when
reading an inval record) and slower (more wal records).  I can easily
develop a patch for that, the question is what we do on the back
branches...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: more parallel query documentation
Next
From: Alvaro Herrera
Date:
Subject: Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.