| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server. |
| Date: | 2010-02-15 07:33:22 |
| Message-ID: | 4B78F8C2.602@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Fujii Masao wrote:
> On Sat, Feb 13, 2010 at 4:33 AM, Richard Huxton <dev(at)archonet(dot)com> wrote:
>> 2. Why have a finish.replication file, rather than "SELECT
>> pg_finish_replication()"?
>
> I thought that the trigger file method was more easy-to-use for the
> existing users since it had been used in pg_standby for a long time
> so far. So I used it.
Also, you might not want to open the standby for connections (ie.
recovery_connections='off'). And even if you wanted, it might not open
because of some of the corner-case limitations in Hot Standby, so you
wouldn't be able to failover.
> But I agree that activating the standby via
> SQL would be useful for some cases.
Yeah.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2010-02-15 08:36:31 | Re: [COMMITTERS] pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after |
| Previous Message | Fujii Masao | 2010-02-15 07:23:13 | Re: Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leonardo F | 2010-02-15 08:26:19 | [FWD] About "Our CLUSTER implementation is pessimal" patch |
| Previous Message | Richard Huxton | 2010-02-15 07:31:14 | Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl |