Re: FATAL: bogus data in lock file "postmaster.pid": "" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: FATAL: bogus data in lock file "postmaster.pid": ""
Date
Msg-id 27691.1346216186@sss.pgh.pa.us
Whole thread Raw
In response to Re: FATAL: bogus data in lock file "postmaster.pid": ""  (Bruce Momjian <bruce@momjian.us>)
Responses Re: FATAL: bogus data in lock file "postmaster.pid": ""
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> On Wed, Aug 29, 2012 at 12:24:26AM -0400, Alvaro Herrera wrote:
>> It's a pretty strange line wrap you got in this version of the patch.
>> Normally we just let the string run past the 78 char limit, without
>> cutting it in any way.  And moving the start of the string to the line
>> following "errhint(" looks very odd to me.

> OK, updated patch attached.

I agree with Alvaro's complaint that moving the whole string literal to
the next line isn't conformant to our usual coding style.  Definitely
nitpicky, but why would you do it like that?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Amit kapila
Date:
Subject: Re: [WIP] Performance Improvement by reducing WAL for Update Operation
Next
From: Benedikt Grundmann
Date:
Subject: Re: MySQL search query is not executing in Postgres DB