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:57:38
Message-ID: CA+U5nMKcuUgmCBuPUXV2zD2C2K+RCC3tQ_QLuJ-vmYQmdWbkMQ@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:

> Where was the discussion of
> why this change should be back-patched?

Your question has broader implications. Currently commit messages do
not reference the conversations that led to them and a great many use
entirely different descriptions on-list and in the commit message, nor
are entries added to conversations to reflect commits.

I share your pain in not being able to follow or remember what led to
many of them. In fact, I'm pretty sure more than a few commits have no
public discussion at all, though mostly there is good discussion.

I'm happy to follow any agreed process we lay out.

--
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 Magnus Hagander 2014-07-15 20:03:28 pgsql: Move check for SSL_get_current_compression to run on mingw
Previous Message Simon Riggs 2014-07-15 19:43:15 Re: [COMMITTERS] pgsql: Reset master xmin when hot_standby_feedback disabled.

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2014-07-15 20:11:12 Re: Allowing NOT IN to use ANTI joins
Previous Message Tom Lane 2014-07-15 19:55:58 Re: Allowing NOT IN to use ANTI joins