| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reopen logfile on SIGHUP |
| Date: | 2018-02-27 23:39:18 |
| Message-ID: | 20180227233918.dyqg5lx5edfmwz2l@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-02-27 16:20:28 -0700, David G. Johnston wrote:
> On Tue, Feb 27, 2018 at 4:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > IOW, I think a fair response to this is "if you're using logrotate with
> > Postgres, you're doing it wrong". That was of some use back before we
> > spent so much sweat on the syslogger, but it's not a reasonable setup
> > today.
> >
>
> A couple of weeks ago a message was posted to general [1] in which I
> concluded the desired behavior is not supported natively. I'm curious
> whether better advice than mine can be given ...
>
> https://www.postgresql.org/message-id/flat/CAKoQ0XHAy9De1C8gxUWHSW6w5iKcqX03wyWGe_%2Bc8NxJccCBHw%40mail(dot)gmail(dot)com#CAKoQ0XHAy9De1C8gxUWHSW6w5iKcqX03wyWGe_+c8NxJccCBHw(at)mail(dot)gmail(dot)com
That link appears to be broken. Real one
https://www.postgresql.org/message-id/CAKoQ0XHAy9De1C8gxUWHSW6w5iKcqX03wyWGe_+c8NxJccCBHw@mail.gmail.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-27 23:45:15 | Re: Reopen logfile on SIGHUP |
| Previous Message | David G. Johnston | 2018-02-27 23:20:28 | Re: Reopen logfile on SIGHUP |