Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id A1C71634272 for ; Wed, 13 May 2009 16:06:32 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 27151-03 for ; Wed, 13 May 2009 16:06:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail137157.authsmtp.co.uk (outmail137157.authsmtp.co.uk [62.13.137.157]) by mail.postgresql.org (Postfix) with ESMTP id 4F1416341EE for ; Wed, 13 May 2009 16:06:31 -0300 (ADT) Received: from mail-c189.authsmtp.com (mail-c189.authsmtp.com [62.13.128.71]) by punt7.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n4DJ6Htu081111; Wed, 13 May 2009 20:06:17 +0100 (BST) Received: from [192.168.0.2] (85-211-96-202.dyn.gotadsl.co.uk [85.211.96.202]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n4DJ6G69012903; Wed, 13 May 2009 20:06:16 +0100 (BST) Subject: Re: New trigger option of pg_standby From: Simon Riggs To: Tom Lane Cc: Heikki Linnakangas , Fujii Masao , Guillaume Smet , Peter Eisentraut , Kevin Grittner , pgsql-hackers In-Reply-To: <14554.1242240824@sss.pgh.pa.us> References: <3f0b79eb0903242329j12865d55s348f5c873a956e71@mail.gmail.com> <1239381103.16396.30.camel@ebony.2ndQuadrant> <3f0b79eb0904122252t1f4c5860v919d199f399ccf72@mail.gmail.com> <3f0b79eb0904132241p18084914g792cb8e5ab3eebb3@mail.gmail.com> <3f0b79eb0904150101pb1c59a3ubb422867e8e6a944@mail.gmail.com> <49EE1E3F.9050307@enterprisedb.com> <3f0b79eb0904212209i7fbd8b68k71db1fef09c62751@mail.gmail.com> <49F01D79.8020805@enterprisedb.com> <3f0b79eb0904230515p751b5248n6ef96880617db055@mail.gmail.com> <4A095A39.3030100@enterprisedb.com> <3f0b79eb0905130127u3a3275b1w79f4d8cb729ded36@mail.gmail.com> <4A0A86D2.9080602@enterprisedb.com> <1985.1242234105@sss.pgh.pa.us> <4A0B10C7.2040309@enterprisedb.com> <14554.1242240824@sss.pgh.pa.us> Content-Type: text/plain Date: Wed, 13 May 2009 20:08:52 +0100 Message-Id: <1242241732.3843.482.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 22d98370-3ff1-11de-bc7b-001f29070be2 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksacRtFaQZbYFhI HGQLW11EUl17WWV/ ag0fZQBDYEtPQQxs TkpJQE1QEQdtHhxP WBpqKB8FcQxGeXx5 ZUUsXHNbWAp4dxJ0 Sk1TFXAFMzFhdWEe BBVFJVBTIh5Kfh4T aFl/U3NfNGdJBC9q VzwTFhsSEA9kHWxz Tx5FMUgTTkkGBHY7 XwwDGjNnGkNNXyoE NAAvLFIWDS41 X-Authentic-SMTP: 61633235383639.kestrel.dmpriest.net.uk:1562/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200905/590 X-Sequence-Number: 138132 On Wed, 2009-05-13 at 14:53 -0400, Tom Lane wrote: > Heikki Linnakangas writes: > > Tom Lane wrote: > >> Does this conclusion mean that changing pg_standby is no longer > >> on the table for 8.4? It certainly smells more like a new feature > >> than a bug fix. > > > This whole thing can be considered to be a new feature. It's working as > > designed. But people seem to be surprised about the current behavior (me > > included), and we don't currently provide the behavior that most people > > actually want. I think we should fix it for 8.4. > > Well, that's okay by me if it can be done in a timely fashion. Bear in > mind that we are planning to wrap beta2 not much more than 24 hours from > now. I'll write it now then, so it can be reviewed tomorrow. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support