Re: [HACKERS] Deadlock with pg_dump?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Chris Campbell <chris(at)bignerdranch(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Deadlock with pg_dump?
Date: 2007-03-02 18:51:32
Message-ID: 15421.1172861492@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Are people going to be happy that log_statement and
> log_min_duration_statement output the statement twice?

If those are the only cases you're worried about, a far simpler solution
is to clear debug_query_string before instead of after emitting those
log messages.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2007-03-02 18:52:14 WITH/RECURSIVE plans
Previous Message Tom Lane 2007-03-02 18:49:14 Re: GIST and TOAST

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-03-02 18:54:18 Re: A little COPY speedup
Previous Message Gregory Stark 2007-03-02 18:51:16 Re: A little COPY speedup