| From: | "Thomas Swan" <tswan(at)idigx(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | tswan(at)idigx(dot)com, "Andrew Hammond" <ahammond(at)ca(dot)afilias(dot)info>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: rotatelogs integration in pg_ctl |
| Date: | 2004-04-13 18:23:38 |
| Message-ID: | 56951.199.222.14.2.1081880618.squirrel@www.idigx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
<quote who="Peter Eisentraut">
> Thomas Swan wrote:
>> Is there a reason the postmasters cannot just close/reopen-recreate
>> the log file when a SIGHUP or other signal is issued like apache?
>
> Yes, because there is no "log file". The postmaster writes to stdout or
> stderr.
>
>
Ok, my misunderstanding. stdout/stderr are redirected to a file on
startup. This is why when I move/rename the logfile I have to stop/start
postgresql to start appending to the empty file.
Would there be any interest in modifying postmaster to support native file
logging in addition to stderr and stdout output? Are there any terrible
drawbacks that you could foresee?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-04-13 18:27:29 | Re: Lexing with different charsets |
| Previous Message | Magnus Hagander | 2004-04-13 18:22:56 | FRONTEND in ecpg |