Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 6A07BB606AB
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Thu,  2 Jun 2011 11:31:54 -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 79444-06; Thu,  2 Jun 2011 14:31:47 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-pv0-f174.google.com (mail-pv0-f174.google.com
	[74.125.83.174])
	by mail.postgresql.org (Postfix) with ESMTP id 0F311B5DF49;
	Thu,  2 Jun 2011 11:31:45 -0300 (ADT)
Received: by pvg12 with SMTP id 12so409210pvg.19
	for <multiple recipients>; Thu, 02 Jun 2011 07:31:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=hl3+7iMyLStAhstSz1R8tqmt1Okeb6eE34YNy7pZys0=;
	b=r/HpTvsoKFkfZ5DBkyM5styOXV5WF6Np2iNjMRDkrb310jEeZ9cDFSvoCNtetreaCC
	7+ka3Yw95g3AR/9uuxw5pmDZimvELugXTqzfx+xv+k2L9v5Tn6D8qIDiFkWzhr1DFZuG
	6UAhSebn7PVibar+sX0ot8DRh0jzFhbxp2EHU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=FasW1iVr2W2fkn1liJJaHM9miea0Q+Qfv7YQ5d/Chb2cDN2m7i4v8llvR2aMKtlN3V
	apgwdlUzOBKmncL26E/XKdSqFqrCrNF6HffSl1oSZ47jZB2PCEVTQnHPnNjsRr7inZpl
	YjvpYBvMRd/IRMcTD/j5T6JeQbMZS0GJy0gwI=
MIME-Version: 1.0
Received: by 10.68.52.105 with SMTP id s9mr314998pbo.245.1307025106074; Thu,
	02 Jun 2011 07:31:46 -0700 (PDT)
Received: by 10.68.56.70 with HTTP; Thu, 2 Jun 2011 07:31:46 -0700 (PDT)
In-Reply-To: <27741.1306968830@sss.pgh.pa.us>
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>
Date: Thu, 2 Jun 2011 10:31:46 -0400
Message-ID: <BANLkTingyUTptpHVPENFsEfMn4fSP5WH+g@mail.gmail.com>
Subject: Re: pgpool versus sequences
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tatsuo Ishii <ishii@postgresql.org>, mangoo@wpkg.org,
	scott.marlowe@gmail.com, t-ishii@sra.co.jp, Kevin.Grittner@wicourts.gov,
	pgsql-hackers@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.898 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001
X-Spam-Level: 
X-Archive-Number: 201106/121
X-Sequence-Number: 188834

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. =A0I 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.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company