| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Chris Campbell <chris(at)bignerdranch(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Deadlock with pg_dump? |
| Date: | 2006-10-26 23:23:12 |
| Message-ID: | 20061026232312.GH31183@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> [ Memo to hackers: why is it that log_min_error_statement = error
> isn't the default? ]
I think it default to panic because it's the way to disable the feature,
which was the easiest sell when the feature was introduced. I'm all for
lowering it to error.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Campbell | 2006-10-27 00:27:31 | Re: Deadlock with pg_dump? |
| Previous Message | Tom Lane | 2006-10-26 22:45:08 | Re: Deadlock with pg_dump? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Campbell | 2006-10-27 00:27:31 | Re: Deadlock with pg_dump? |
| Previous Message | Jeremy Drake | 2006-10-26 22:58:07 | psql \lo_* quiet mode patch |