CSVlog vs tabs - Mailing list pgsql-hackers

From Andrew Dunstan
Subject CSVlog vs tabs
Date
Msg-id 46732BF9.5090909@dunslane.net
Whole thread Raw
Responses Re: CSVlog vs tabs  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: CSVlog vs tabs  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: CSVlog vs tabs  ("FAST PostgreSQL" <fastpgs@fast.fujitsu.com.au>)
List pgsql-hackers
Now that we've fixed the partial/interleaved log line issue, I have 
returned to trying toi get the CSV log patch into shape. Sadly, it still 
needs lots of work, even after Greg Smith and I both attacked it, so I 
am now going through it with a fine tooth comb.

One issue I notice is that it mangles the log message to add a tab 
character before each newline. We do this in standard text logs to make 
them more readable for humans. but the whole point of having CSV logs is 
to make them machine readable, and I'm rather inclined to think this 
sort of behaviour is both unnecessary and undesirable.  So I'm intending 
to leave it out for CSV logs.

Comments?

cheers

andrew


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: currtid_byreloid and currtid_byrelname
Next
From: "Joshua D. Drake"
Date:
Subject: Re: CSVlog vs tabs