Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id B12F2636BAB for ; Fri, 27 Mar 2009 11:36:13 -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 85015-01 for ; Fri, 27 Mar 2009 11:36:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail137186.authsmtp.net (outmail137186.authsmtp.net [62.13.137.186]) by mail.postgresql.org (Postfix) with ESMTP id E555F6341E7 for ; Fri, 27 Mar 2009 11:36:08 -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 n2REZwUO041662; Fri, 27 Mar 2009 14:35:58 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 n2REZufc048952; Fri, 27 Mar 2009 14:35:57 GMT Subject: Re: New trigger option of pg_standby From: Simon Riggs To: Tom Lane Cc: Peter Eisentraut , Guillaume Smet , Fujii Masao , Kevin Grittner , pgsql-hackers In-Reply-To: <8365.1238163943@sss.pgh.pa.us> 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> <8365.1238163943@sss.pgh.pa.us> Content-Type: text/plain Date: Fri, 27 Mar 2009 14:36:36 +0000 Message-Id: <1238164596.16568.604.camel@ebony.2ndQuadrant> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Server-Quench: 95af3ecb-1adc-11de-aecc-001871e930f4 X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksacBtFagJbYFhD HGQLW11EUVl7WmZ/ bg0fZQBDYEtPQQdo U1ZAQE1QEQdtHhxP WBx8J3M3IVZGfHZ5 YEQsXHNZXApzcBcr QRsHR3AHNDMzdWEe 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/1146 X-Sequence-Number: 135824 On Fri, 2009-03-27 at 10:25 -0400, Tom Lane wrote: > Peter Eisentraut writes: > > 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 :-) > > +1 for using a "-m something" type of syntax instead of having to try to > pick single-letter switches that are mnemonic for the different cases. > But -1 to those particular mode names --- I think it will invite > confusion with pg_ctl's behavior. The choice is between * one parameter with the option being given as text within trigger file * two parameters naming different types of trigger file I don't mind which, as long as it is one of those two, unless there is a third way to specify things so that user has control at failover time. A single -m option would hardcode that decision ahead of time, which is undesirable behaviour, hence the additional complexity being discussed. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support