| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Beattie <mtbeedee(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FATAL: bogus data in lock file "postmaster.pid": "" |
| Date: | 2012-08-29 02:28:55 |
| Message-ID: | 24583.1346207335@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-08-29 02:42:18 | Re: "default deny" for roles |
| Previous Message | Bruce Momjian | 2012-08-29 02:21:27 | Re: FATAL: bogus data in lock file "postmaster.pid": "" |