Re: logging problem ... ?

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: logging problem ... ?
Дата
в 13:24:39
Msg-id
2864.957806630@sss.pgh.pa.us
Ответ на
Re: logging problem ... ? (The Hermit Hacker)
Список
Дерево обсуждения
logging problem ... ? The Hermit Hacker <scrappy@hub.org>
Re: logging problem ... ? Tom Lane <tgl@sss.pgh.pa.us>
Re: logging problem ... ? The Hermit Hacker <scrappy@hub.org>
Re: logging problem ... ? Tom Lane <tgl@sss.pgh.pa.us>
Re: logging problem ... ? The Hermit Hacker <scrappy@hub.org>
Re: logging problem ... ? Tom Lane <tgl@sss.pgh.pa.us>
Re: logging problem ... ? The Hermit Hacker <scrappy@hub.org>
Re: logging problem ... ? Peter Eisentraut <peter_e@gmx.net>
The Hermit Hacker  writes:
> cat ~pgsql/pgstart ... postmaster's own debug output?  ya know, for some
> stupid reason, the only thing i'm capturing is postgres's output :(  I
> just modified the pgstart script and restarted the server, so postmaster's
> output is to logs/postmaster.5432 ...

Oh, I see the problem!  It's the -S in the postmaster switches:

${POSTMASTER} -d 1 -B 4096 -N 128 -S \                                 ^^

That redirects postmaster's stdout/stderr to /dev/null, so you never
see anything in its log except for a message or two that comes out
before -S is processed.  Instead of -S you should be using

nohup ${POSTMASTER} same-switches-except-S \& logs/postmaster.${PORT}  &

(I'm not sure if redirecting stdin to /dev/null is really necessary on
your OS, but it is on mine.)
		regards, tom lane

В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
Сообщение: Re: So we're in agreement....
От: Mike Wyer
Дата:
FAQ