Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e6CH6pW09645 for ; Wed, 12 Jul 2000 13:06:51 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id NAA23416; Wed, 12 Jul 2000 13:06:36 -0400 (EDT) To: Antti Linno cc: pgsql-sql@postgresql.org Subject: Re: Opposite of LOCK In-reply-to: References: Comments: In-reply-to Antti Linno message dated "Wed, 12 Jul 2000 11:11:03 +0300" Date: Wed, 12 Jul 2000 13:06:36 -0400 Message-ID: <23413.963421596@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/133 Antti Linno writes: > Is there any possibility to unlock tables after they've been locked? The > manual part of lock was fuzzy, so I ask from experts instead. MySQL > uses lock and unlock. Locks are released at transaction commit/abort. It has to be that way to preserve transaction semantics. I'll refrain from commenting about MySQL's transaction support... regards, tom lane