| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Simon(at)2ndquadrant(dot)com" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Eric Kerin" <eric(at)bootseg(dot)com>, mendola(at)bigfoot(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: will PITR in 8.0 be usable for "hot spare"/"log shipping" type of replication |
| Date: | 2004-08-14 15:29:46 |
| Message-ID: | 5009.1092497386@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Simon(at)2ndquadrant(dot)com" <simon(at)2ndquadrant(dot)com> writes:
>> Tom Lane wrote:
>> Right, also an area that needs thought. Some other people opined that
>> they want the switchover to occur only on manual command. I'd go with
>> that too if you have anything close to 24x7 availability of admins.
>> If you *must* have automatic switchover, what's the safest criterion?
>> Dunno, but let's think ...
> That's fairly straightforward.
> You use a recovery_command that sleeps when it discovers a full log file
> isn't available - i.e. it has requested the "last" or master-current WAL
> file. The program wakes when the decision/operator command to switchover is
> taken.
But you're glossing over the hard part, which is how to take that
decision (assuming that for some reason you can't afford to wait for
a human to make it).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-08-14 16:03:16 | Re: Turkish downcasting in PL/pgSQL |
| Previous Message | Tom Lane | 2004-08-14 15:21:46 | Re: Turkish downcasting in PL/pgSQL |