Re: selective statement logging - Mailing list pgsql-hackers

From Tom Lane
Subject Re: selective statement logging
Date
Msg-id 13758.1078959891@sss.pgh.pa.us
Whole thread Raw
In response to Re: selective statement logging  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: selective statement logging  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: selective statement logging  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: unsafe floats
Next
From: "Thomas Swan"
Date:
Subject: Re: [GENERAL] Shouldn't B'1' = 1::bit be true?