Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7ELZZP29312 for ; Tue, 14 Aug 2001 17:35:35 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f7ELZVY20554; Tue, 14 Aug 2001 17:35:31 -0400 (EDT) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: Deadlocks? What happened to MVCC? In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Tue, 14 Aug 2001 12:15:52 -0700" Date: Tue, 14 Aug 2001 17:35:31 -0400 Message-ID: <20551.997824931@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200108/195 X-Sequence-Number: 4427 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. regards, tom lane