From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | depesz <depesz(at)depesz(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] BUG #3799: csvlog skips some logs |
Date: | 2007-12-06 18:04:01 |
Message-ID: | 20071206180401.GI8451@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Tom Lane wrote:
> "depesz" <depesz(at)depesz(dot)com> writes:
> > Description: csvlog skips some logs
>
> The point here is that CSV-format log output doesn't include the
> DETAIL, HINT, or context (QUERY/STATEMENT/CONTEXT) lines that
> you might get with normal output.
>
> I suppose this was intentional in order to keep the CSV output
> format manageable, but I have to wonder whether it's really a
> good idea. I can see the argument that you probably don't need
> to log HINTs, but the other stuff might be important. Particularly
> the STATEMENT.
Hmm. I think it could be a problem in cases where an error message with
identical wording is disambiguated by context. In my VH opinion we
shouldn't be losing log info just because we're using a different
format.
--
Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34J
"Linux transformó mi computadora, de una `máquina para hacer cosas',
en un aparato realmente entretenido, sobre el cual cada día aprendo
algo nuevo" (Jaime Salinas)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-12-06 18:08:43 | Re: [HACKERS] BUG #3799: csvlog skips some logs |
Previous Message | Simon Riggs | 2007-12-06 17:27:14 | Re: BUG #3790: pg_restore error canceling statement due touser request |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-12-06 18:07:32 | Re: pg_dump and BINARY mode COPY |
Previous Message | Tom Lane | 2007-12-06 17:43:50 | Re: pg_dump and BINARY mode COPY |