Re: [COMMITTERS] pgsql: Make fast promotion the default promotion mode.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Make fast promotion the default promotion mode.
Date: 2013-05-01 12:20:58
Message-ID: CA+U5nMLPZUvXHHXoVFcbwG6-NC-GC_y_-Mq=GFXUUBJ-JE75=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 1 May 2013 11:25, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Apr 24, 2013 at 8:49 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> Make fast promotion the default promotion mode.
>> Continue to allow a request for synchronous
>> checkpoints as a mechanism in case of problems.
>
> Is there clean way to request synchronous checkpoint at the standby promotion?
> I'm sure that we can do that by creating the file "promote" and
> sending the SIGUSR1
> signal to the postmaster. Or by using previous version of pg_ctl.
> These are not clean
> and would confuse users.

I just removed the user interface at Heikki's request, so yes, I can
see its not ideal interface.

My wish was to have a mechanism should we need it.

A third option would be to not have any way at all.

What is your preference?

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2013-05-01 13:55:45 Re: [COMMITTERS] pgsql: Make fast promotion the default promotion mode.
Previous Message Fujii Masao 2013-05-01 10:25:13 Re: [COMMITTERS] pgsql: Make fast promotion the default promotion mode.

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2013-05-01 13:55:45 Re: [COMMITTERS] pgsql: Make fast promotion the default promotion mode.
Previous Message Adrian.Vondendriesch 2013-05-01 11:59:02 Re: BUG #8128: pg_dump (>= 9.1) failed while dumping a scheme named "old" from PostgreSQL 8.4