Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

pgsql-hackers by date

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

pgsql-patches by date

Next:From: Tom LaneDate: 2007-03-02 18:54:18
Subject: Re: A little COPY speedup
Previous:From: Gregory StarkDate: 2007-03-02 18:51:16
Subject: Re: A little COPY speedup

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group