Re: New trigger option of pg_standby - Mailing list pgsql-hackers

From Guillaume Smet
Subject Re: New trigger option of pg_standby
Date
Msg-id 1d4e0c10903250848x4e067c86ue611c0c50f25e49d@mail.gmail.com
Whole thread Raw
In response to Re: New trigger option of pg_standby  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: New trigger option of pg_standby  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Wed, Mar 25, 2009 at 2:59 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> I find it hard to imagine a use case for the existing default
> behavior.

I thought a bit about it and I think it can be useful when your
priority is the availability of the service and you don't consider a
data loss that important: even if you have a lot of WALs segments to
replay, you may want to have your service up immediately in case of a
major problem.

Keeping it is a good idea IMHO but I don't think it should be the default.

-- 
Guillaume


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: improving concurrent transactin commit rate
Next
From: Sam Mason
Date:
Subject: Re: improving concurrent transactin commit rate