| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "depesz" <depesz(at)depesz(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: BUG #3799: csvlog skips some logs |
| Date: | 2007-12-06 17:10:55 |
| Message-ID: | 16585.1196961055@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"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.
Comments?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-12-06 17:27:14 | Re: BUG #3790: pg_restore error canceling statement due touser request |
| Previous Message | Alvaro Herrera | 2007-12-06 15:24:45 | Re: BUG #3790: pg_restore error canceling statement due touser request |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-12-06 17:30:02 | pg_dump and BINARY mode COPY |
| Previous Message | Tom Lane | 2007-12-06 16:48:36 | Re: shared_buffers, wal_buffers, WAL files, data files |