On Thu, Aug 30, 2012 at 03:02:28PM -0400, Robert Haas wrote:
> On Thu, Aug 30, 2012 at 2:08 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > On Thu, Aug 30, 2012 at 05:28:17PM +0000, Robert Haas wrote:
> >> Add missing period to detail message.
> >>
> >> Per note from Peter Eisentraut.
> >>
> >> Branch
> >> ------
> >> REL8_3_STABLE
> >>
> >> Details
> >> -------
> >> http://git.postgresql.org/pg/commitdiff/588fb3f01f7159990a9bfabb578615c3c32ffc6e
> >>
> >> Modified Files
> >> --------------
> >> src/backend/storage/lmgr/proc.c |    2 +-
> >> 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > I didn't think we backpatched error string changes because of
> > translation churn.
> 
> Well, the patch that this was related to was back-patched, so I
> figured this should be, too.  That concern did cross my mind, though.
> I can revert in the back branches if the translations team prefers.

Oh, if the patch was backpatched, the error message churn probably isn't
a problem then.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

• Re: pgsql: Add missing period to detail message. at 2012-08-30 19:02:28 from Robert Haas

Responses

• Re: pgsql: Add missing period to detail message. at 2012-08-30 19:30:15 from Tom Lane

pgsql-committers by date

Next:	From: Robert Haas	Date: 2012-08-30 19:10:19
	Subject: pgsql: Fix checkpoint_timeout documentation to reflect currentbehavior
Previous:	From: Robert Haas	Date: 2012-08-30 19:02:28
	Subject: Re: pgsql: Add missing period to detail message.