Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP
	id 906F04765A0; Thu, 21 Nov 2002 14:22:18 -0500 (EST)
Received: from jester.senspire.com (unknown [216.208.117.7])
	by postgresql.org (Postfix) with ESMTP
	id AA5A5476588; Thu, 21 Nov 2002 14:22:17 -0500 (EST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by jester.senspire.com (8.12.6/8.12.6) with ESMTP id gALJMkhU078724;
	Thu, 21 Nov 2002 14:22:47 -0500 (EST) (envelope-from rbt@rbt.ca)
Subject: Re: [HACKERS] [GENERAL] Bug with sequence
From: Rod Taylor <rbt@rbt.ca>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: "Thomas O'Connell" <tfo@monsterlabs.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	pgsql-sql@postgresql.org
In-Reply-To: <200211211911.gALJB8G21214@candle.pha.pa.us>
References: <200211211911.gALJB8G21214@candle.pha.pa.us>
Content-Type: text/plain
Organization: 
Message-Id: <1037906566.56165.6.camel@jester>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 21 Nov 2002 14:22:46 -0500
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200211/374
X-Sequence-Number: 10516

On Thu, 2002-11-21 at 14:11, Bruce Momjian wrote:
> Of course, those would be SQL purists who _don't_ understand
> concurrency issues.  ;-)

Or they're the kind that locks the entire table for any given insert.

-- 
Rod Taylor <rbt@rbt.ca>