Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 4C954476E6E
	for <pgsql-sql@postgresql.org>; Fri,  1 Nov 2002 14:48:10 -0500 (EST)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id A51FE476E6C
	for <pgsql-sql@postgresql.org>; Fri,  1 Nov 2002 14:48:09 -0500 (EST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id gA1JlihR001009;
	Fri, 1 Nov 2002 14:47:44 -0500 (EST)
To: Wei Weng <wweng@kencast.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: FIFO Queue Problems 
In-reply-to: <1036178317.23296.2.camel@Monet> 
References: <20021101145630.50886.qmail@web13801.mail.yahoo.com>
	<26900.1036169461@sss.pgh.pa.us> <1036178317.23296.2.camel@Monet>
Comments: In-reply-to Wei Weng <wweng@kencast.com>
	message dated "01 Nov 2002 14:18:37 -0500"
Date: Fri, 01 Nov 2002 14:47:44 -0500
Message-ID: <1008.1036180064@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200211/17
X-Sequence-Number: 10159

Wei Weng <wweng@kencast.com> writes:
> Do you need to unlock the table fifo when you are done?

That happens at COMMIT.

			regards, tom lane