From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: What does log_destination = csvlog mean? |
Date: | 2009-06-15 19:20:37 |
Message-ID: | 200906151920.n5FJKbU15585@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
> > In reading through our documentation, I am unclear how "log_destination
> > = csvlog" works. It seems to me that 'cvslog' is a format-output type,
> > not a real destination, or rather it is a special output format for
> > stderr. Is this accurate? I would like to clarify our documentation.
> >
> >
>
> CSV logs can in fact only be delivered via redirected stderr, i.e.
> csvlog requires that logging_collector be on. So in a sense it's both a
> format and a destination.
>
> There is a strong technical reason for that, namely that only by doing
> that can be be sure that CSV logs won't get lines multiplexed, which
> would make loading them back into a table impossible. We invented a
> whole (simple) protocol between the backends and the syslogger just to
> handle that.
That's what I thought; thanks.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-06-15 23:58:16 | Re: char() overhead on read-only workloads not so insignifcant as the docs claim it is... |
Previous Message | Andrew Dunstan | 2009-06-15 19:14:25 | Re: What does log_destination = csvlog mean? |