Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 5B940632AD2 for ; Fri, 27 Mar 2009 10:08:55 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 61918-08 for ; Fri, 27 Mar 2009 10:08:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail137067.authsmtp.co.uk (outmail137067.authsmtp.co.uk [62.13.137.67]) by mail.postgresql.org (Postfix) with ESMTP id DF463632A95 for ; Fri, 27 Mar 2009 10:08:51 -0300 (ADT) Received: from mail-c188.authsmtp.com (mail-c188.authsmtp.com [62.13.128.25]) by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n2RD8l2x090247; Fri, 27 Mar 2009 13:08:47 GMT Received: from [192.168.0.4] (85-211-223-92.dyn.gotadsl.co.uk [85.211.223.92]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id n2RD8ja5017906; Fri, 27 Mar 2009 13:08:45 GMT Subject: Re: New trigger option of pg_standby From: Simon Riggs To: Guillaume Smet Cc: Peter Eisentraut , Fujii Masao , Kevin Grittner , pgsql-hackers In-Reply-To: <1d4e0c10903270519p556649bfr9b19f9156c43be4b@mail.gmail.com> References: <3f0b79eb0903242329j12865d55s348f5c873a956e71@mail.gmail.com> <1d4e0c10903242350i505a9f6bsa7ba347dc02f90b6@mail.gmail.com> <3f0b79eb0903250144k453b3927mffa8b08678ed057b@mail.gmail.com> <1d4e0c10903250155w34bd79dcvfab2ad5c95e56011@mail.gmail.com> <49C9F255.EE98.0025.0@wicourts.gov> <1d4e0c10903250848x4e067c86ue611c0c50f25e49d@mail.gmail.com> <3f0b79eb0903251851v5936d6b4x49997ac8f04b98b9@mail.gmail.com> <1d4e0c10903260032v767da1fdg6cf7cea86c64cc45@mail.gmail.com> <1238064633.16568.420.camel@ebony.2ndQuadrant> <49CCBEE0.1080307@gmx.net> <1d4e0c10903270519p556649bfr9b19f9156c43be4b@mail.gmail.com> Content-Type: text/plain Date: Fri, 27 Mar 2009 13:09:24 +0000 Message-Id: <1238159364.16568.600.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 678ed6c7-1ad0-11de-aecc-001871e930f4 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksacxtFagJbYFhD HGQLW11EUV57WWt/ bwwfZQBDYEtPQQdo U1ZAQE1QEQdtHhxP WBx8JhEoJgBGeXl5 ZUAsXHFYWAp8ck4o FkgHEnAHNDNgdWEe BBVFJlYHIx5Kfh5N bVEqXXANN2FJBC9q VzwTFhsSEA9kHWxz Tx5FMUgTTkkGBHY7 XwwDGjNnGkNNXyoE NAAvLFIWDS41 X-Authentic-SMTP: 61633235383639.cat.dmpriest.net.uk:1378/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200903/1137 X-Sequence-Number: 135815 On Fri, 2009-03-27 at 13:19 +0100, Guillaume Smet wrote: > On Fri, Mar 27, 2009 at 12:56 PM, Peter Eisentraut wrote: > > Simon Riggs wrote: > >> > >> If we go with this, I would suggest we make *neither* the default by > >> removing -t, and adopting two new options: something like -f == fast > >> failover, -p == patient failover. > > > > -m smart|fast|immediate :-) > > The advantage of having 2 options (or the ability to put a string > value in the trigger file) is that you can choose the behaviour when > you need to trigger it (you just have to use the 2 options with 2 > different filenames). I don't think it's the case with your proposal. Yes, sorry. I meant we should use the naming Peter suggests. So we would have two triggers, but call them fast and smart, rather than fast and patient. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support