Re: [HACKERS] more robust log rotation

2007-06-05 Thread Andrew Dunstan



Tom Lane wrote:

Andrew Dunstan <[EMAIL PROTECTED]> 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



---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] more robust log rotation

2007-06-05 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> 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...

regards, tom lane

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq