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, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Deadlock with pg_dump?
Date: 2007-02-26 20:15:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> This is not the first GUC that has needed this.

Exactly.  I think that we simply made a mistake in the initial
implementation of log_min_error_statement: we failed to think about
whether it should use client or server priority ordering, and the
easy-to-code behavior was the wrong one.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Jeff McKennaDate: 2007-02-26 20:17:15
Subject: Re: Compile libpq for pg8.2.3 with vc7
Previous:From: Bruce MomjianDate: 2007-02-26 20:13:53
Subject: Re: Simple Column reordering

pgsql-patches by date

Next:From: Robert TreatDate: 2007-02-26 21:01:11
Subject: FAQ_DEV Update: Fix Answer for Q 1.19, add Q on SCMS
Previous:From: Bruce MomjianDate: 2007-02-26 20:10:49
Subject: Re: [HACKERS] Deadlock with pg_dump?

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