| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: A single escape required for log_filename |
| Date: | 2009-01-13 22:18:43 |
| Message-ID: | 20090113221843.GH4656@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Joshua D. Drake (jd(at)commandprompt(dot)com) wrote:
> On Tue, 2009-01-13 at 16:58 -0500, Tom Lane wrote:
> > 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.
>
> copytruncate resolves this issue does it not? On that note it seems
> maybe that is a smart idea (to reopen the log). PostgreSQL will already
> allow you to arbitrarily change the log_filename with a HUP.
It would certainly be nice to have a way to cause PostgreSQL to reopen
it's log file without disrupting operation. That's a much better option
than using copytruncate.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-01-13 22:29:39 | So, what locale should the regression tests run in? |
| Previous Message | Stephen Frost | 2009-01-13 22:16:03 | Re: A single escape required for log_filename |