From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | sthomas(at)optionshouse(dot)com |
Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fast promotion, loose ends |
Date: | 2013-04-22 15:45:27 |
Message-ID: | CA+U5nML-z5wywt-Lm8Ma-ruH9dj-8YrvKFOwFNXyeLx_3riq6A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 22 April 2013 16:09, Shaun Thomas <sthomas(at)optionshouse(dot)com> wrote:
> On 04/22/2013 02:58 AM, Simon Riggs wrote:
>
>> So, to initiate promotion, you can create a file called
>> $DATADIR/fast_promote or $DATADIR/promote
>
>
> Pardon my naiveté, but could it also be an option to read the method from
> the promotion file?
>
> echo "slow" > /my/promotion/path
>
> That would work without any default naming scheme, and only incurs a read on
> the file-handle.
We could do that and a similar mechanism existed in pg_standby, but
was removed in 9.0.
Given where we are and the shape of the code I'd rather not do that.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-04-22 16:04:41 | Re: event trigger API documentation? |
Previous Message | Simon Riggs | 2013-04-22 15:44:00 | Re: Fast promotion, loose ends |