Re: more robust log rotation

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: more robust log rotation
Date: 2007-06-05 22:34:45
Message-ID: 4665E505.9090106@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> My thought is to have the logger mark each true log line line end with a
>> null byte.
>>
>
> This seems not to help much when you consider interleaved output from
> different backends...
>
>
>

True. We have two problems with log robustness, and this was an attempt
to address one of them. I sent some thoughts about interleaving
yesterday. If you have any thoughts about handling interleaving then I'm
all ears. However, my impression was that this only happened on a small
number of platforms. If it's more general then it's all the more urgent
to fix. ISTM that we can't really consider CSV logging until we have a
handle on both problems.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2007-06-06 03:02:51 Re: Implicit casts with generic arrays
Previous Message Tom Lane 2007-06-05 22:00:54 Re: more robust log rotation