Re: [HACKERS] Deadlock with pg_dump? - Mailing list pgsql-patches

From Simon Riggs
Subject Re: [HACKERS] Deadlock with pg_dump?
Date
Msg-id 1172518309.3760.375.camel@silverbirch.site
Whole thread Raw
In response to Re: [HACKERS] Deadlock with pg_dump?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Deadlock with pg_dump?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Mon, 2007-02-26 at 14:28 -0500, Tom Lane wrote:
> "Simon Riggs" <simon@2ndquadrant.com> writes:
> > The idea of the patch is that it generates a log message which then
> > invokes log_min_error_statement so that the SQL statement is displayed.
> > LOG is not on the list of options there, otherwise I would use it.
>
> As I said, you don't understand how the logging priority control works.
> LOG *is* the appropriate level for stuff intended to go to the server log.

Please look at the definition of log_min_error_statement, so you
understand where I'm coming from.

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



pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Deadlock with pg_dump?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Deadlock with pg_dump?