Search Postgresql Archives

Re: Postgres logs to syslog LOCAL0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bruce Momjian <pgman@xxxxxxxxxxxxxxxx> 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):

       The parameter ident in the call of openlog() is probably stored  as-is.
       Thus,  if  the  string  it  points  to  is  changed, syslog() may start
       prepending the changed string, and if the string it points to ceases to
       exist,  the  results  are  undefined.  Most portable is to use a string
       constant.

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.

However, that doesn't explain the change in facility ...

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux