From: | momjian(at)postgresql(dot)org |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src/backend/utils/error (elog.c) |
Date: | 2000-11-25 04:38:01 |
Message-ID: | 200011250438.eAP4c1S63461@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Date: Friday, November 24, 2000 @ 23:38:00
Author: momjian
Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/utils/error
from hub.org:/home/projects/pgsql/tmp/cvs-serv63445/pgsql/src/backend/utils/error
Modified Files:
elog.c
----------------------------- Log Message -----------------------------
> > Looking some more, I found some other places that need a space (I
> > suspect...), so here is an updated patch.
>
> This seems like the wrong way to go about it, because anytime anyone
> changes any elog output anywhere, we'll risk another failure. If
> syslog can't cope with empty lines, I think the right fix is for the
> output-to-syslog routine to change the data just before sending ---
> then there is only one place to fix. See the syslog output routine in
> src/backend/utils/error/elog.c.
Makes sense. Here's a new patch, now the output even looks better:
Larry Rosenman
From | Date | Subject | |
---|---|---|---|
Next Message | momjian | 2000-11-25 05:00:28 | pgsql/doc/src/sgml (func.sgml) |
Previous Message | momjian | 2000-11-25 04:32:13 | pgsql/src/interfaces/jdbc/org/postgresql/jdbc2 (DatabaseMetaData.java) |