Re: Should we remove "not fast" promotion at all?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Tomonari Katsumata <t(dot)katsumata1122(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tomonari Katsumata <katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should we remove "not fast" promotion at all?
Date: 2013-08-19 16:44:47
Message-ID: 20130819164447.GD9087@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 19, 2013 at 11:20:42AM +0300, Heikki Linnakangas wrote:
> And it's even worse if you use 9.3 pg_ctl against a 9.2 server: it
> will create a filed called "fast_promote" and return success, but it
> won't actually do anything.
>
> I think "promote" file should trigger the fast promotion, and the
> filename to trigger the slow mode should be called
> "fallback_promote" or "safe_promote" or something like that. There
> wasn't any good reason to change the filename primarily used. It
> might even break people's scripts for no good reason, if people are
> creating the $PGDATA/promote file themselves without using pg_ctl.
>
> (I raised this back in April, but Simon argued strongly for the
> current situation. I never understood why.
> http://www.postgresql.org/message-id/517798AE.30203@vmware.com)

+1

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-08-19 16:57:44 Re: [BUGS] 9.3beta2: Failure to pg_upgrade
Previous Message 'Bruce Momjian' 2013-08-19 16:26:35 Re: 9.3 release notes suggestions