"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> 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 *mu
> Tom Lane
> Eric Kerin <[EMAIL PROTECTED]> writes:
> > The issues I've seen are:
> > 1. Knowing when the master has finished the file transfer transfer to
> > the backup.
>
> The "standard" solution to this is you write to a temporary file name
> (generated off your process PID, or some other conv
Eric Kerin <[EMAIL PROTECTED]> writes:
> The issues I've seen are:
> 1. Knowing when the master has finished the file transfer transfer to
> the backup.
The "standard" solution to this is you write to a temporary file name
(generated off your process PID, or some other convenient reasonably-
uniqu
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> It should work; dunno if anyone has tried it yet.
> I was thinking about it but I soon realized that actually is
> impossible to do, postgres replay the log only if during the
> start the file recover.conf is present in $DATA directo
Hannu Krosing <[EMAIL PROTECTED]> writes:
> will PITR in 8.0 be usable for "hot spare"/"log shipping" type of
> replication or is it just for Point In Time RECOVERY ?
It should work; dunno if anyone has tried it yet.
regards, tom lane
---(end of br
will PITR in 8.0 be usable for "hot spare"/"log shipping" type of
replication or is it just for Point In Time RECOVERY ?
---
Hannu
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org
