From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: serverlog rotation/functions |
Date: | 2004-07-14 15:04:02 |
Message-ID: | 40F54B62.7050409@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> That struck me as not only useless but the deliberately hard way to do
> it. To use that in the real world, you'd have to set up a cron job to
> trigger the rotation,
Still on my radar...
which means a lot of infrastructure and privilege;
> whereas ISTM the point of this feature was to avoid both.
... I was thinking about putting this into the pg_autovacuum process.
The log
> capture process should just do its own rotation on a pre-configured
> time-interval basis, and/or maximum-file-size basis.
Yup.
I see zero value
> added in having it respond to external signals.
I see >0 value. I like to truncate my logfile before doing some
complicated stuff, to have a handy file for debugging purposes.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB SD | 2004-07-14 15:17:43 | Re: Portals and nested transactions |
Previous Message | Tom Lane | 2004-07-14 13:20:08 | Re: [HACKERS] Point in Time Recovery |
From | Date | Subject | |
---|---|---|---|
Next Message | markw | 2004-07-14 15:55:52 | Re: [HACKERS] Point in Time Recovery |
Previous Message | Tom Lane | 2004-07-14 15:00:39 | Re: PITR Archive Recovery plus WIP PITR |