From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tatsuo Ishii <ishii@postgresql.org>
Cc: mangoo@wpkg.org
Cc: scott.marlowe@gmail.com
Cc: t-ishii@sra.co.jp
Cc: Kevin.Grittner@wicourts.gov
Cc: pgsql-hackers@postgresql.org
Subject: Re: pgpool versus sequences
Date: Thu, 02 Jun 2011 15:54:30 -0400
Message-ID: <27667.1307044470@sss.pgh.pa.us> (raw)
In-Reply-To: <BANLkTingyUTptpHVPENFsEfMn4fSP5WH+g@mail.gmail.com>
References: <16063.1306811813@sss.pgh.pa.us>
<4DE4A652.2040301@wpkg.org>
<25524.1306848814@sss.pgh.pa.us>
<20110601.001430.1098605953350881110.t-ishii@sraoss.co.jp>
<26909.1306965898@sss.pgh.pa.us>
<BANLkTikCRTeZ_g-rDay4RukWOY3Q7irCnQ@mail.gmail.com>
<27741.1306968830@sss.pgh.pa.us>
<BANLkTingyUTptpHVPENFsEfMn4fSP5WH+g@mail.gmail.com>
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Jun 1, 2011 at 6:53 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Please note also that what pgpool users have got right now is a time
>> bomb, which is not better than immediately-visible breakage. I would
>> prefer to try to get this change out ahead of widespread adoption of the
>> broken pgpool version.
> Hmm, I gather from what Tatsuo is saying at the web site that this has
> only been broken since the release of 3.0 on February 23rd, so given
> that I think your approach makes sense.
Done, and I also installed a kluge to clean up the damage retroactively
during any nextval/setval operation.
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, ishii@postgresql.org, mangoo@wpkg.org, scott.marlowe@gmail.com, t-ishii@sra.co.jp, Kevin.Grittner@wicourts.gov, pgsql-hackers@postgresql.org
Subject: Re: pgpool versus sequences
In-Reply-To: <27667.1307044470@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