| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Bruce Momjian" <bruce(at)momjian(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:31:49 |
| Message-ID: | 1172518309.3760.375.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, 2007-02-26 at 14:28 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2007-02-26 19:36:58 | Re: SCMS question |
| Previous Message | Simon Riggs | 2007-02-26 19:28:29 | Re: Simple Column reordering |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-26 19:52:03 | Re: [HACKERS] Deadlock with pg_dump? |
| Previous Message | Tom Lane | 2007-02-26 19:28:26 | Re: [HACKERS] Deadlock with pg_dump? |