From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: CSVlog vs tabs |
Date: | 2007-06-16 00:22:39 |
Message-ID: | 46732D4F.7000808@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
> 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?
I would agree. The only thing we need is whatever the CSV delimiter.
Joshua D. Drake
>
> cheers
>
> andrew
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | Tasneem Memon | 2007-06-16 00:46:55 | Re: To all the pgsql developers..Have a look at the operators proposed by me in my researc |
Previous Message | Andrew Dunstan | 2007-06-16 00:16:57 | CSVlog vs tabs |