| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| 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:28:26 |
| Message-ID: | 5030.1172518106@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-02-26 19:28:29 | Re: Simple Column reordering |
| Previous Message | Jeff McKenna | 2007-02-26 19:23:58 | Compile libpq for pg8.2.3 with vc7 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-02-26 19:31:49 | Re: [HACKERS] Deadlock with pg_dump? |
| Previous Message | Simon Riggs | 2007-02-26 19:19:49 | Re: [HACKERS] Deadlock with pg_dump? |