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

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, 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 14:51:32
Message-ID: 1376923892.9929.YahooMailNeo@web162902.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:

>> 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.
>
> +1.

+1  Changing it has risk with no associated benefit that I can see.
 
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2013-08-19 15:04:49 Re: Fix Windows socket error checking for MinGW
Previous Message Alvaro Herrera 2013-08-19 14:49:33 Re: Fix Windows socket error checking for MinGW