X-Original-To: pgsql-bugs@postgresql.org
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id 5D6EB475CBC
	for <pgsql-bugs@postgresql.org>; Fri, 21 Mar 2003 00:34:34 -0500 (EST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2L5YYub010124;
	Fri, 21 Mar 2003 00:34:34 -0500 (EST)
To: bruc@acm.org
Cc: pgsql-bugs@postgresql.org
Subject: Re: Bug report 
In-reply-to: <200303210026.h2L0Qnes092115@stone.congenomics.com> 
References: <200303210026.h2L0Qnes092115@stone.congenomics.com>
Comments: In-reply-to "Robert E. Bruccoleri" <bruc@stone.congenomics.com>
	message dated "Thu, 20 Mar 2003 19:26:49 -0500"
Date: Fri, 21 Mar 2003 00:34:34 -0500
Message-ID: <10123.1048224874@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200303/124
X-Sequence-Number: 5684

"Robert E. Bruccoleri" <bruc@stone.congenomics.com> writes:
> The PostgreSQL backend core dumps reproducibly with a set of LOCK commands that
> would normally deadlock.

Can't duplicate that here, using either 7.3 branch or CVS tip.  You sure
you have a clean build?

			regards, tom lane