Skip site navigation (1) Skip section navigation (2)

Re: syslogger line-end processing infelicity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: syslogger line-end processing infelicity
Date: 2007-06-01 21:33:31
Message-ID: 24146.1180733611@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I have been looking at the syslogger code in connection with the CSV log 
> output proposal, and I'm quite concerned about the way it translates 
> every \n into \r\n for Windows output.
> ...
> My second thought is that we should quite possibly abandon this 
> translation altogether

+1 on that.  The problem of ensuring atomic output remains though
(see nearby complaints from George Pavlov and others).  It's bad enough
in the existing logging context, but if we're hoping to make
easily-machine-readable logs it's a "must fix".

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-06-01 21:36:13
Subject: Re: query log corrupted-looking entries
Previous:From: Bruce MomjianDate: 2007-06-01 21:31:52
Subject: Upcoming events

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group