| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | jd(at)commandprompt(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: A single escape required for log_filename |
| Date: | 2009-01-13 22:16:03 |
| Message-ID: | 20090113221602.GG4656@tamriel.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > I have perfectly good log rotation utility that exists on my OS. (yes I
> > am aware of the possibility of losing a log entry when using logrotate).
>
> You might think you do, but it won't work with PG; external rotators
> only work with programs that respond to SIGHUP by re-opening their log
> files.
logrotate will work well enough using copytruncate. It's certainly
unfortunate that PostgreSQL doesn't provide a better mechanism.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2009-01-13 22:18:43 | Re: A single escape required for log_filename |
| Previous Message | Stephen Frost | 2009-01-13 22:13:55 | Re: A single escape required for log_filename |