On Sun, 8 Aug 2004, Andreas Pflug wrote:
> Marc G. Fournier wrote:
>
>>> Basically I think you will need a vote to expand this in 8.1.
>>
>>
>> Hate to ask, but can someone summarize what it is that is being
>> "discussed" here? Andreas' post about 'size triggering' is what drew my
>> eye, but I think I missed the central point :(
>
> Summary:
>
> The patch I originally posted (in June) implemented a log rotation, which was
> triggered by call to a function, not automatically (subject to a
> to-be-written surveillance process), and implemented inside elog.c (more or
> less). Tom had many objections, and this emerged to the current
> implementation of a subprocess that will do rotation automatically dependent
> on size and/or age limits and seems valuable.
'k, for me, as long as it has these two, I'm happy ... that falls in line
with all the ones that I'm used to ...
> My postings also included manual triggering of logfile switching,
> catching SIGUSR1 (from SendPostmasterSignal) and setting the flag which
> otherwise is set by exceeding of configured size/age limit or a
> postgresql.conf settings change (SIGHUP triggered).
The only 'server' that I've ever seen this in was aolserver ... and I wish
they'd implement per-size/age ones instead :(
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
