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

From Tom Lane
Subject Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.
Date
Msg-id 30429.1460753617@sss.pgh.pa.us
Whole thread Raw
In response to Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.  (Andres Freund <andres@anarazel.de>)
Responses Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> 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.

No objection to that part.  What I'm saying is that when there isn't one,
the answer is a new record type, not forcing xid assignment.  It might
look almost like a commit record, but it shouldn't imply that there
was a transaction.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.
Next
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Add new catalog called pg_init_privs