Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2T05sU29562 for ; Wed, 28 Mar 2001 19:05:54 -0500 (EST) (envelope-from gutz@kalador.com) Received: from van12d7.dial.uniserve.ca ([204.244.161.70] helo=gutz) by mail2.uniserve.com with smtp (Exim 3.13 #1) id 14iPwk-0004LU-00 for pgsql-sql@postgresql.org; Wed, 28 Mar 2001 16:05:50 -0800 From: "Gerald Gutierrez" To: Subject: Can a SELECT block? Date: Wed, 28 Mar 2001 16:10:58 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Archive-Number: 200103/594 X-Sequence-Number: 2264 Hi all. I'm trying to track down a deadlock problem caused by some automatically generated SQL code. It seems I'm deadlocking on a table that is actually quite rarely modified. I'm unsure, but it appears that maybe something is blocking on a SELECT call. Under what situations can a SELECT block? I'm assuming that a simple INSERT probably cannot block anywhere. Under what situations, aside from two UPDATEs to the same row, can an UPDATE block? I'd appreciate any time. To give some details, it appears that my application server (Orion) is holding connections to the database, some of which are not in transactions, and some of which are "primed" for connections (meaning that a BEGIN is always issued, and waits till transactional work needs to be done, at which point it issues a COMMIT and then another BEGIN and waits again). It seems to always issue the command "SET TRANSACTION ISOLATION LEVEL READ COMMITTED" after each BEGIN. I'd appreciate any help that anyone can give. Thanks. Gerald.