From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | guillaume(dot)smet(at)gmail(dot)com |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New trigger option of pg_standby |
Date: | 2009-03-26 01:51:08 |
Message-ID: | 3f0b79eb0903251851v5936d6b4x49997ac8f04b98b9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Thu, Mar 26, 2009 at 12:48 AM, Guillaume Smet
<guillaume(dot)smet(at)gmail(dot)com> wrote:
> On Wed, Mar 25, 2009 at 2:59 PM, Kevin Grittner
> <Kevin(dot)Grittner(at)wicourts(dot)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.
Yes, I also think that this is likely use case.
> Keeping it is a good idea IMHO but I don't think it should be the default.
What does "the default" mean? You mean that new trigger should use
the existing trigger option character (-t)?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2009-03-26 02:09:20 | Re: Mentors needed urgently for SoC & PostgreSQL Student Internships |
Previous Message | Bruce Momjian | 2009-03-26 01:34:18 | Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try |