Re: pgsql: Resolve timing issue with logging locks for Hot Standby.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Resolve timing issue with logging locks for Hot Standby.
Date: 2012-01-30 16:24:04
Message-ID: 4F26C424.5090504@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-01-30 16:38:21 Re: pgsql: Resolve timing issue with logging locks for Hot Standby.
Previous Message Tom Lane 2012-01-30 15:45:48 Re: pgsql: Resolve timing issue with logging locks for Hot Standby.