Re: pgsql: Resolve timing issue with logging locks for Hot Standby. - Mailing list pgsql-committers

From Andrew Dunstan
Subject Re: pgsql: Resolve timing issue with logging locks for Hot Standby.
Date
Msg-id 4F26C424.5090504@dunslane.net
Whole thread Raw
In response to Re: pgsql: Resolve timing issue with logging locks for Hot Standby.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Resolve timing issue with logging locks for Hot Standby.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers

On 01/30/2012 10:45 AM, Tom Lane wrote:
> Another aspect of this is that when the same-or-almost-the-same patch
> is applied to multiple branches, it's a *lot* easier for future
> archeology in the commit logs if the patch goes into all the affected
> branches at the same time (and with the same commit message, please).

Yeah, I've been pinged on this before, for exactly this reason. It makes
release note preparation significantly easier, AIUI.

cheers

andrew

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Resolve timing issue with logging locks for Hot Standby.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Resolve timing issue with logging locks for Hot Standby.