From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>, Chris Campbell <chris(at)bignerdranch(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Deadlock with pg_dump? |
Date: | 2007-02-14 03:19:54 |
Message-ID: | 200702140319.l1E3Jsa07208@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-02-14 03:30:42 | Re: Deadlock with pg_dump? |
Previous Message | Bruce Momjian | 2007-02-14 03:19:15 | Re: Deadlock with pg_dump? |