Re: [HACKERS] Deadlock with pg_dump?
| От | Simon Riggs |
|---|---|
| Тема | Re: [HACKERS] Deadlock with pg_dump? |
| Дата | |
| Msg-id | 1172518309.3760.375.camel@silverbirch.site обсуждение |
| Ответ на | Re: [HACKERS] Deadlock with pg_dump? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [HACKERS] Deadlock with pg_dump?
|
| Список | 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 по дате отправления: