Skip site navigation (1) Skip section navigation (2)

Re: Deadlock with pg_dump?

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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.

In response to

pgsql-hackers by date

Next:From: Chris CampbellDate: 2006-10-27 00:27:31
Subject: Re: Deadlock with pg_dump?
Previous:From: Tom LaneDate: 2006-10-26 22:45:08
Subject: Re: Deadlock with pg_dump?

pgsql-patches by date

Next:From: Chris CampbellDate: 2006-10-27 00:27:31
Subject: Re: Deadlock with pg_dump?
Previous:From: Jeremy DrakeDate: 2006-10-26 22:58:07
Subject: psql \lo_* quiet mode patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group