Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id BEA96632C5B for ; Wed, 27 May 2009 10:38:16 -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 32715-02 for ; Wed, 27 May 2009 10:38:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail137184.authsmtp.co.uk (outmail137184.authsmtp.co.uk [62.13.137.184]) by mail.postgresql.org (Postfix) with ESMTP id 4AB696326A7 for ; Wed, 27 May 2009 10:38:10 -0300 (ADT) Received: from mail-c189.authsmtp.com (mail-c189.authsmtp.com [62.13.128.71]) by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n4RDbxVv023665; Wed, 27 May 2009 14:37:59 +0100 (BST) Received: from [192.168.0.2] (85-211-225-42.dyn.gotadsl.co.uk [85.211.225.42]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n4RDbwUM082860; Wed, 27 May 2009 14:37:59 +0100 (BST) Subject: Re: New trigger option of pg_standby From: Simon Riggs To: Bruce Momjian Cc: Tom Lane , Heikki Linnakangas , Fujii Masao , Guillaume Smet , Peter Eisentraut , Kevin Grittner , pgsql-hackers In-Reply-To: <200905271313.n4RDDg404900@momjian.us> References: <200905271313.n4RDDg404900@momjian.us> Content-Type: text/plain Date: Wed, 27 May 2009 14:41:18 +0100 Message-Id: <1243431678.24860.186.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 97d91961-4ac3-11de-a90b-001f29070be2 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksafhtFagJbYFhI HGQLW11EUVl7WmR/ bgMfZQBDYEtPQQdo VVZNQE1QEQdtHhxP WBp8Jks1EnhGcHx4 Y0YsXHFZXQpzchJ0 Q0dSFHACNDRjdWEe BBVFJgpUIh5Kfh4T 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-Status: No virus detected - but ensure you scan with your own anti-virus system. 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/1100 X-Sequence-Number: 138642 On Wed, 2009-05-27 at 09:13 -0400, Bruce Momjian wrote: > Tom Lane wrote: > > Heikki Linnakangas writes: > > > I don't think we're going to get this to work reliably without extending > > > the interface between the backend and restore_command. We've discussed > > > many methods and there's always some nasty corner-case like that. > > > > > I think we should leave back-branches as is, and go with Simon's > > > suggestion to add new "recovery_end_command" that's run when the > > > recovery is finished. That's simpler and more reliable than any of the > > > other approaches we've discussed, and might become handy for other > > > purposes as well. > > > > > Does someone want to take a stab at writing a patch for that? > > > > 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. > > I think the big frustration is that this issue was first brought up > March 25 and it took two months to resolve it, at which point we were in > beta. I think many hoped a better idea would emerge but often that just > doesn't happen and we have to do the best fix we can and move on. I agree, very frustrating. Why do you bring it up again now? -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support