Hello
I'm using the latest Postgres version, and I'm trying to get rid of the PID
of the backend when logging to syslogd. After seeing it's not doable, I
looked at the source only to find:
openlog(Syslog_ident, LOG_PID | LOG_NDELAY, syslog_fac);
Re-reading the docs, I see no mention of the fa
Ymir <[EMAIL PROTECTED]> writes:
> I'm using the latest Postgres version, and I'm trying to get rid of the PID
> of the backend when logging to syslogd.
Seems like a fairly bad idea, since you'll then be unable to distinguish
the log outputs from multiple Postgres backends running concurrently.
Has this been addressed? Can you supply a reproducable example?
---
Edward Pilipczuk wrote:
> On Monday, 22 April 2002 18:41, you wrote:
> > Edward ([EMAIL PROTECTED]) reports a bug with a severity of 1
> > The lower the n
David Kaplan ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
dump/reinstall fails with local sameuser security
Long Description
I recently upgraded to postgresql-7.2.1-5. Before doing so I did a pg_dumpall and
then after upgr
