CSVlog vs tabs

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: CSVlog vs tabs
Date: 2007-06-16 00:16:57
Message-ID: 46732BF9.5090909@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2007-06-16 00:22:39 Re: CSVlog vs tabs
Previous Message Gregory Stark 2007-06-15 23:17:23 Re: currtid_byreloid and currtid_byrelname