| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logging stuff |
| Date: | 2003-08-05 22:38:52 |
| Message-ID: | 13773.1060123132@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> ... And of course, we already have pid and timestamp, so once
> we are done, we will have seven possible data items on each line, and
> with booleans there will be no control over their order on the line.
Which is exactly the way I want it ;-). I can't see any use that would
justify the amount of extra logic needed to allow user-specified
ordering of the entries. This feature discussion seems to be
degenerating into a gild-the-lily contest ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Tenny | 2003-08-05 22:40:40 | PostgreSQL JDBC driver Connection.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE) failures |
| Previous Message | Dave Tenny | 2003-08-05 22:35:32 | PostgreSQL JDBC driver Connection.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE) failures |