Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.
Date: 2016-04-14 15:50:58
Message-ID: CA+TgmoaQHya-XPgeyKv+SFj3x4uhaz-x-4n2+scOfwLPi77Dvw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 13, 2016 at 9:58 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> We've recently discussed a very similar issue around
> http://www.postgresql.org/message-id/20160227002958.peftvmcx4dxwe244@alap3.anarazel.de
>
> Unfortunately Simon over in that thread disagreed there about fixing
> this by always emitting a commit record when nmsgs > 0 in
> RecordTransactionCommit(). I think this thread is a pretty strong hint
> that we actually should do so.

Yes. I'm pretty confident that you had the right idea there, and that
Simon's objection was off-base.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-04-14 15:52:00 Re: Pglogical questions and problems
Previous Message Robert Haas 2016-04-14 15:49:01 Re: SET ROLE and reserved roles