Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] Postgres logs to syslog LOCAL0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: han(dot)holl(at)informationslogik(dot)nl
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: [GENERAL] Postgres logs to syslog LOCAL0
Date: 2005-10-17 13:57:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-general
han(dot)holl(at)informationslogik(dot)nl writes:
> On Friday 14 October 2005 19:05, you wrote:
>> [ redirecting to a more appropriate list ]
>>> +preload_libraries =
>>> '/usr/prod/postgres/rubriek:rub_initialize,/usr/prod/postgres/drap,/usr/p
>>> rod/postgres/naam'
>> Han, what are these libraries?  Is it possible that any of them are
>> issuing openlog() calls?
> Yes, it does:
> static void log_error(const char *mess, int code)
> {
>         openlog("PG_FETCH", 0, LOG_LOCAL0);
>         syslog(LOG_ERR, "%s %d", mess, code);
>         closelog();
> }

> I didn't think of this because I didn't see the PG_FETCH in the log.

Well, that explains both the disappearance of the LOG_PID bit and the
reversion to LOCAL0 ... I think.  One issue is that if that openlog()
call overrode our original one, then why didn't we see PG_FETCH in the
log messages?

What platform are you on, exactly?  I'm hoping it's something we can
look at the source of openlog for ...

			regards, tom lane

In response to


pgsql-bugs by date

Next:From: Eduardo SoaresDate: 2005-10-17 17:00:21
Subject: BUG #1972: index error with space character
Previous:From: Yogaraj. CDate: 2005-10-17 11:50:29
Subject: BUG #1971: Start Transaction is giving Errors !!!

pgsql-general by date

Next:From: Marc G. FournierDate: 2005-10-17 13:58:17
Subject: Re: Oracle buys Innobase
Previous:From: Cristian PrietoDate: 2005-10-17 13:54:08
Subject: Re: dynamic loading of .so

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group