From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: selective statement logging |
Date: | 2004-03-10 23:44:41 |
Message-ID: | 200403102344.i2ANifo21372@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > If people are happy with suppressing statement logging on a parse error,
> > OK.
>
> I think that's a really, really awful idea. Not infrequently, the
> postmaster log is the easiest way of debugging applications that are
> sending bogus SQL. If you fail to log the bogus SQL then you've just
> cut debuggers off at the knees.
>
> I haven't read the earlier part of the thread yet so I don't know just
> what problem you want to solve, but please not this solution.
The issue is allowing only logging of DDL statements, or DDL and data
modification statements, as listed on the TODO list. If they ask for
all statements, certainly we should log all statements.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-03-10 23:51:48 | Re: selective statement logging |
Previous Message | Jonathan Gardner | 2004-03-10 23:27:26 | Re: How to get RelationName ?? |