On Thu, 2005-06-02 at 01:13 +0300, [EMAIL PROTECTED] wrote:
> In this case do you know what is the timeout on the "restore_command"
> command (or where I can find it in documentation).
There isn't one. You decide when restore_command returns.
> What will happen if I make the restore command wait
thanks for your reply,
I did not presume that it is a bug, I am interested to know how can I
setup a "hot standby" (if is some more documentation available).
===QUOTE FROM DOCS===
If we continuously feed the series of WAL files to another machine that
has been loaded with the same base backu
On Mon, 2005-05-23 at 16:17 +0300, Postgres General wrote:
> I am trying to setup a "hot standby" on a second machine.
> I have created a "recovery.conf" file and started a restore with logs
> from the primary machine. everything was OK.
>
> now a have new transaction logs generated by the primar
On Mon, 2005-05-23 at 10:14, Douglas McNaught wrote:
> Postgres General <[EMAIL PROTECTED]> writes:
>
> > what is the procedure for creating a "hot standby" (continuously
> > feeding a series of WAL files created by the primary machine into the
> > secondary one) ?
>
> There currently isn't one.
Postgres General <[EMAIL PROTECTED]> writes:
> what is the procedure for creating a "hot standby" (continuously
> feeding a series of WAL files created by the primary machine into the
> secondary one) ?
There currently isn't one. I think someone may be working on it.
-Doug
hello,
I am trying to setup a "hot standby" on a second machine.
I have created a "recovery.conf" file and started a restore with logs
from the primary machine. everything was OK.
now a have new transaction logs generated by the primary machine and I
want to "play" them on the secondary one.
