From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: tgl <tgl@sss.pgh.pa.us>
Cc: robertmhaas <robertmhaas@gmail.com>
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: Wed, 01 Jun 2011 19:47:06 -0400
Message-ID: <1306971997-sup-5549@alvh.no-ip.org> (raw)
In-Reply-To: <20110602.080816.460114267356667394.t-ishii@sraoss.co.jp>
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>
Excerpts from Tatsuo Ishii's message of mié jun 01 19:08:16 -0400 2011:
> What pgpool really wanted to do was locking sequence tables, not
> locking rows in sequences. I wonder why the former is not allowed.
Yeah -- why is LOCK SEQUENCE foo_seq not allowed? Seems a simple thing
to have.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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: alvherre@commandprompt.com, ishii@postgresql.org, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, mangoo@wpkg.org, scott.marlowe@gmail.com, kevin.grittner@wicourts.gov, pgsql-hackers@postgresql.org
Subject: Re: pgpool versus sequences
In-Reply-To: <1306971997-sup-5549@alvh.no-ip.org>
* 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