Re: [GENERAL] Postgres logs to syslog LOCAL0

2005-10-14 Thread han . holl
On Friday 14 October 2005 17:06, Tom Lane wrote: > > This is troubling since a reload of the config file could well move > things around. We should probably pass strdup(Syslog_ident) to openlog, > not just Syslog_ident. > I can confirm that we use reload quite a lot to switch between full statemen

Re: [GENERAL] Postgres logs to syslog LOCAL0

2005-10-14 Thread Tom Lane
Bruce Momjian writes: > I don't see any SELECT: entry in there. In fact, SELECT: is coming from > syslog, not from PostgreSQL. We only generate the stuff after the > closing ]. The SELECT: is probably coming from syslog_ident. I note the following comment in the Linux man page for syslog(3):

Re: [GENERAL] Postgres logs to syslog LOCAL0

2005-10-14 Thread Bruce Momjian
I tested LOCAL5 here and got lines like: Oct 14 08:41:06 candle postgres[8668]: [1-1] LOG: duration: 1.210 ms statement: select 100; I don't see any SELECT: entry in there. In fact, SELECT: is coming from syslog, not from PostgreSQL. We only generate the stuff after the closi