Re: selective statement logging - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: selective statement logging
Date
Msg-id 200403102344.i2ANifo21372@candle.pha.pa.us
Whole thread Raw
In response to Re: selective statement logging  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: selective statement logging  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Jonathan Gardner
Date:
Subject: Re: How to get RelationName ??
Next
From: Andrew Dunstan
Date:
Subject: Re: selective statement logging