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 23:38:54
Message-ID: 22134.1172878734@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:
> Tom Lane wrote:
>> It wouldn't really be any different from errcode(), but if you want
>> I'll do it.

> If you would just add the infrastructure I can add the LOG part.

OK, I applied a patch that covers the same territory as your patch of
Wednesday evening. I didn't do anything about Simon's original patch
--- I assume that needs some rework now.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2007-03-02 23:39:02 SE-Linux/PostgreSQL work?
Previous Message Bruce Momjian 2007-03-02 23:34:33 Re: broken doc

Browse pgsql-patches by date

  From Date Subject
Next Message David Fetter 2007-03-02 23:40:16 Arrays of Complex Types
Previous Message FAST PostgreSQL 2007-03-02 23:13:10 Re: [PATCHES] WIP Patch - Updateable Cursors