From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Tatsuo Ishii <ishii@postgresql.org>
Cc: mangoo <mangoo@wpkg.org>
Cc: scott.marlowe <scott.marlowe@gmail.com>
Cc: Kevin.Grittner <kevin.grittner@wicourts.gov>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: pgpool versus sequences
Date: Thu, 02 Jun 2011 10:31:58 -0400
Message-ID: <14930.1307025118@sss.pgh.pa.us> (raw)
In-Reply-To: <BANLkTimgVA7mi2SP_ZVH-fsUB3VShTsMng@mail.gmail.com>
References: <26909.1306965898@sss.pgh.pa.us>
<BANLkTikCRTeZ_g-rDay4RukWOY3Q7irCnQ@mail.gmail.com>
<27741.1306968830@sss.pgh.pa.us>
<20110602.080816.460114267356667394.t-ishii@sraoss.co.jp>
<1306971997-sup-5549@alvh.no-ip.org>
<BANLkTimgVA7mi2SP_ZVH-fsUB3VShTsMng@mail.gmail.com>
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Jun 1, 2011 at 7:47 PM, Alvaro Herrera
> <alvherre@commandprompt.com> 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
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, alvherre@commandprompt.com, ishii@postgresql.org, mangoo@wpkg.org, scott.marlowe@gmail.com, kevin.grittner@wicourts.gov, pgsql-hackers@postgresql.org
Subject: Re: pgpool versus sequences
In-Reply-To: <14930.1307025118@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