| From: | daveg <daveg(at)sonic(dot)net> |
|---|---|
| To: | FAST PostgreSQL <fastpgs(at)fast(dot)fujitsu(dot)com(dot)au> |
| Cc: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: WIP patch - INSERT-able log statements |
| Date: | 2007-02-21 22:00:11 |
| Message-ID: | 20070221220011.GB11978@sonic.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Thu, Feb 22, 2007 at 11:50:06AM +1100, FAST PostgreSQL wrote:
> - The log output will be in COPY format and will include the following
> information, irrespective of the log_line_prefix setting.
> ( timestamp_with_milliseconds, timestamp, username, databasename,
> sessionid, host_and_port, host, proc_id, command_tag, session_start,
> transaction_id, error_severity, SQL_State_Code, statement/error_message);
Why are there two timestamps?
What about durations? Do they include all this?
Is the statement log written when the statement starts or when it completes?
-dg
--
David Gould daveg(at)sonic(dot)net
If simplicity worked, the world would be overrun with insects.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-02-21 22:08:53 | Re: autovacuum next steps, take 2 |
| Previous Message | Stephan Szabo | 2007-02-21 21:51:55 | Re: Column storage positions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-21 22:16:02 | Re: [previously on HACKERS] "Compacting" a relation |
| Previous Message | Bruce Momjian | 2007-02-21 20:02:19 | Re: [HACKERS] Dead code in _bt_split? |