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

From Tom Lane
Subject Re: [HACKERS] Deadlock with pg_dump?
Date
Msg-id 12779.1172776640@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
Bruce Momjian <bruce@momjian.us> writes:
> What are *you* thinking?  Yes, that patch has that line, but
> log_statement and log_min_duration_statement is going to trigger
> log_min_error_statement so you are going to get the statement printed
> twice.

What's wrong with that?  If a statement triggers two different log
entries, and both are subject to being annotated with the statement text
according to log_min_error_statement, I would expect them both to be
annotated.  Doing otherwise will probably break automated log analysis
tools.

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: A little COPY speedup
Next
From: Heikki Linnakangas
Date:
Subject: Re: A little COPY speedup