pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Guillaume Smet <guillaume.smet@gmail.com>
Cc: Fujii Masao <masao.fujii@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: New trigger option of pg_standby
Date: Fri, 27 Mar 2009 14:36:36 +0000
Message-ID: <1238164596.16568.604.camel@ebony.2ndQuadrant> (raw)
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>


On Fri, 2009-03-27 at 10:25 -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.net> 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




view thread (127+ messages)  latest in thread

Message-ID: <1238164596.16568.604.camel@ebony.2ndQuadrant>
Permalink:  ../1238164596.16568.604.camel@ebony.2ndQuadrant/
Also on:    postgresql.org/message-id/1238164596.16568.604.camel@ebony.2ndQuadrant

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: simon@2ndQuadrant.com, tgl@sss.pgh.pa.us, peter_e@gmx.net, guillaume.smet@gmail.com, masao.fujii@gmail.com, Kevin.Grittner@wicourts.gov
  Subject: Re: New trigger option of pg_standby
  In-Reply-To: <1238164596.16568.604.camel@ebony.2ndQuadrant>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox