Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7EMiNP52547 for ; Tue, 14 Aug 2001 18:44:23 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 102244; Tue, 14 Aug 2001 15:44:20 -0700 From: "Josh Berkus" Subject: Re: Deadlocks? What happened to MVCC? To: Tom Lane Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Tue, 14 Aug 2001 15:44:20 -0700 Message-ID: In-Reply-To: <20551.997824931@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200108/197 X-Sequence-Number: 4429 Tom, Jan, > MVCC does not mean "no locks" ... particularly not when UPDATEs are > involved. You'll need to be more specific about what your function > is > doing, but my first thought would be to look for the possibility of > conflicting updates of the same row. Found the problem after 3 hours and a phone call to PostgreSQL Inc. Turns out that I had one too-broad UPDATE in a 250-line function ... feh! -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco