Re: [HACKERS] Deadlock with pg_dump?

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Chris Campbell" <chris(at)bignerdranch(dot)com>, <pgsql-patches(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Deadlock with pg_dump?
Date: 2007-02-26 19:01:24
Message-ID: 1172516484.3760.346.camel@silverbirch.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Mon, 2007-02-26 at 13:34 -0500, Bruce Momjian wrote:

> I am a little concerned about a log_* setting that is INFO. I understand
> why you used INFO (for log_min_error_messages), but INFO is inconsistent
> with the log* prefix, and by default INFO doesn't appear in the log
> file.

Yeh, LOG would be most appropriate, but thats not possible.

log_min_messages allows only DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1,
INFO, NOTICE and WARNING for non-error states.

Possibly DEBUG1?

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-02-26 19:11:23 Re: [HACKERS] Deadlock with pg_dump?
Previous Message Andrew Hammond 2007-02-26 18:49:23 Re: help required regarding queryin postgis database from google maps

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-26 19:11:23 Re: [HACKERS] Deadlock with pg_dump?
Previous Message Bruce Momjian 2007-02-26 18:39:28 Re: pg_standby Error cleanup