Re: Deadlock with pg_dump? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Deadlock with pg_dump?
Date
Msg-id 200702140319.l1E3Jsa07208@momjian.us
Whole thread Raw
In response to Re: Deadlock with pg_dump?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Deadlock with pg_dump?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> "Albe Laurenz" <all@adv.magwien.gv.at> writes:
> >> [ Memo to hackers: why is it that log_min_error_statement = error
> >> isn't the default? ]
> 
> > To avoid spamming the logs with every failed SQL statement?
> 
> Certainly there are people who will turn it off, but that's why it's
> configurable.  I've had to answer "how do I find out what's causing
> error message FOO" often enough that I'm starting to think logging error
> statements is a more useful default than not logging 'em ...

Are we ready to set 'log_min_error_statement = error' by default for
8.3?

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Deadlock with pg_dump?
Next
From: Tom Lane
Date:
Subject: Re: Deadlock with pg_dump?