Re: [COMMITTERS] pgsql: Reset master xmin when hot_standby_feedback disabled.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Reset master xmin when hot_standby_feedback disabled.
Date: 2014-07-15 19:43:15
Message-ID: CA+U5nMLmH1TTa=EXLkfGwjKco-AFZTe2gUjLZPyg0jiB6KWGxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 15 July 2014 19:15, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> Reset master xmin when hot_standby_feedback disabled.
>> If walsender has xmin of standby then ensure we
>> reset the value to 0 when we change from hot_standby_feedback=on
>> to hot_standby_feedback=off.
>
>> Branch
>> ------
>> REL9_2_STABLE
>
>
> While I'm not necessarily objecting to the content of this patch,
> I do have a problem with the process. Where was the discussion of
> why this change should be back-patched? (If I'm identifying it
> correctly, this is a back-patch of commit bd56e7412, a year and a
> half later. That should have been noted in the commit message, too,
> rather than leaving people to reconstruct why you'd only committed
> into two old branches.)

Sorry if my actions confused.

I kept the commit message deliberately identical to help people, not to confuse.

There was recent discussion of it on-list and a public request to
backpatch, which I agreed with and acknowledged.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2014-07-15 19:57:38 Re: [COMMITTERS] pgsql: Reset master xmin when hot_standby_feedback disabled.
Previous Message Peter Eisentraut 2014-07-15 19:13:40 pgsql: pg_upgrade: Fix spacing in help output

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-07-15 19:55:58 Re: Allowing NOT IN to use ANTI joins
Previous Message Pavel Stehule 2014-07-15 19:34:20 Re: psql: show only failed queries