Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: [HACKERS] Deadlock with pg_dump?
Date
Msg-id 15832.1172727954@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Deadlock with pg_dump?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [HACKERS] Deadlock with pg_dump?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-patches
Tree view 
Bruce Momjian <bruce@momjian.us> writes:
> I have coded up the following patch which places LOG just above ERROR in
> log_min_error_statement.

LOG_NO_STATEMENT?  What *are* you thinking?  The kindest word I can find
for this is "baroque".

What I had in mind was a one-line patch:

    if (edata->elevel >= log_min_error_statement && debug_query_string != NULL)

becomes

    if (is_log_level_output(edata->elevel, log_min_error_statement) && debug_query_string != NULL)

            regards, tom lane

pgsql-patches by date:

Previous
From: Michael Glaesemann
Date:
Subject: Re: Numeric patch to add special-case representations for < 8 bytes
Next
From: Patric Bechtel
Date:
Subject: Re: Numeric patch to add special-case representations for < 8 bytes