Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 6C811B606AB for ; Thu, 2 Jun 2011 11:32:15 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 79319-07 for ; Thu, 2 Jun 2011 14:32:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 6B5A3B606AC for ; Thu, 2 Jun 2011 11:32:08 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p52EVwdP014931; Thu, 2 Jun 2011 10:31:59 -0400 (EDT) To: Robert Haas cc: Alvaro Herrera , Tatsuo Ishii , mangoo , "scott.marlowe" , "Kevin.Grittner" , pgsql-hackers Subject: Re: pgpool versus sequences In-reply-to: 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> Comments: In-reply-to Robert Haas message dated "Thu, 02 Jun 2011 10:28:27 -0400" Date: Thu, 02 Jun 2011 10:31:58 -0400 Message-ID: <14930.1307025118@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201106/122 X-Sequence-Number: 188835 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 We should do that anyway, even if we put in the effort to support the other syntax. regards, tom lane