pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Antti Linno <alligator@all.ee>
Cc: pgsql-sql@postgresql.org
Subject: Re: Opposite of LOCK
Date: Wed, 12 Jul 2000 13:06:36 -0400
Message-ID: <23413.963421596@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.04.10007121109460.19137-100000@all.ee>
References: <Pine.LNX.4.04.10007121109460.19137-100000@all.ee>

Antti Linno <alligator@all.ee> 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



view thread (3+ messages)

Message-ID: <23413.963421596@sss.pgh.pa.us>
Permalink:  ../23413.963421596@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/23413.963421596@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, alligator@all.ee
  Subject: Re: Opposite of LOCK
  In-Reply-To: <23413.963421596@sss.pgh.pa.us>
  References: <Pine.LNX.4.04.10007121109460.19137-100000@all.ee> <23413.963421596@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox