Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 202ACB60741 for ; Thu, 2 Jun 2011 11:55:40 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 31280-01; Thu, 2 Jun 2011 14:55:33 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 061D4B5DD9C; Thu, 2 Jun 2011 11:55:32 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 011A9348045; Thu, 2 Jun 2011 07:55:32 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s6wYsF9aJmaE; Thu, 2 Jun 2011 07:55:30 -0700 (PDT) Received: from perhan.alvh.no-ip.org (unknown [190.95.16.242]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id B7639348044; Thu, 2 Jun 2011 07:55:29 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id E449F6E3F8; Thu, 2 Jun 2011 10:55:26 -0400 (CLT) Content-Type: text/plain; charset=UTF-8 Cc: Robert Haas , Tatsuo Ishii , mangoo , scott.marlowe , Kevin.Grittner , pgsql-hackers Subject: Re: pgpool versus sequences From: Alvaro Herrera To: Tom Lane In-reply-to: <14930.1307025118@sss.pgh.pa.us> References: <26909.1306965898@sss.pgh.pa.us> <27741.1306968830@sss.pgh.pa.us> <20110602.080816.460114267356667394.t-ishii@sraoss.co.jp> <1306971997-sup-5549@alvh.no-ip.org> <14930.1307025118@sss.pgh.pa.us> Date: Thu, 02 Jun 2011 10:55:26 -0400 Message-Id: <1307026309-sup-4021@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201106/137 X-Sequence-Number: 188850 Excerpts from Tom Lane's message of jue jun 02 10:31:58 -0400 2011: > Robert Haas writes: > > On Wed, Jun 1, 2011 at 7:47 PM, Alvaro Herrera > > wrote: > >> Yeah -- why is LOCK SEQUENCE foo_seq not allowed? Seems a simple thing > >> to have. > > > It cause a grammar conflict. > > That's a lot of work for a purely cosmetic issue, though. What would be > trivial is to let this work: > > regression=# create sequence s1; > CREATE SEQUENCE > regression=# begin; > BEGIN > regression=# lock table s1; > ERROR: "s1" is not a table Yeah, though it'd be nice to avoid this: alvherre=# create schema public_too; CREATE SCHEMA alvherre=# set search_path to 'public_too', 'public'; SET alvherre=# create table public_too.s1 (); CREATE TABLE alvherre=# create sequence public.s1; CREATE SEQUENCE alvherre=# begin; BEGIN alvherre=# lock s1; LOCK TABLE At this point we have a lock on the table, but if we change LOCK to also look for sequences, the behavior would change. At the very least, the command tag should be different. Hopefully few people name sequences the same as tables ... -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support