Re: FATAL: bogus data in lock file "postmaster.pid": ""
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Michael Beattie <mtbeedee@gmail.com>, Magnus Hagander <magnus@hagander.net>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-08-29T02:28:55Z
Lists: pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes: > On Tue, Aug 28, 2012 at 04:25:36PM -0400, Tom Lane wrote: >> The backend side of this looks mostly sane to me (but drop the \n, >> messages are not supposed to contain those). But the feof test proposed > Removed. I thought we needed to add \n so that strings >80 would wrap > properly. How do we handle this? We don't. Per the message style guidelines, it's the responsibility of a client frontend to line-wrap such text if it feels the need to. The backend has no business assuming that 80 characters (or any other number) is where to wrap. regards, tom lane