Thanks for the link Simon, but this doesn't recommend any method for
triggering failover, or telling the primary that another server is now
primary.
We've set up a primary server in archive mode to continuously archive to an
NFS mount, and the standby server to continuously recovery from that
On Wed, Feb 25, 2009 at 09:26:26AM +, Thom Brown wrote:
We've set up a primary server in archive mode to continuously archive to an
NFS mount, and the standby server to continuously recovery from that
directory (although I'm not sure that's actually working... I've probably
overlooked
2009/2/25 Karsten Hilbert karsten.hilb...@gmx.net
Think backwards: How would it automatically *dis*appear from
there. Have the secondary create it and check for existance
at regular intervals. Have the primary delete it at slightly
shorter intervals.
When the secondary finds it again after
I'm still trying to work out how this file creation/deletion thing will
work. If I can tag a touch /tmp/pg.trigger command to the end of the
recovery command, how often will that be called? If I can't, I still need
to ensure that it is created and deleted before the recovery command is
called,
On Wed, 2009-02-25 at 13:54 +, Thom Brown wrote:
I'm still trying to work out how this file creation/deletion thing
will work. If I can tag a touch /tmp/pg.trigger command to the
end of the recovery command, how often will that be called? If I
can't, I still need to ensure that it is
You are doing this the hard way. Grab PITRTTools.
https://projects.commandprompt.com/public/pitrtools
I can't really dispute a recommendation from JD. I'll have to look into
that. It's a shame because we've spent ages trying to work out where we've
been going wrong in this whole process
On Wed, 2009-02-25 at 16:33 +, Thom Brown wrote:
You are doing this the hard way. Grab PITRTTools.
https://projects.commandprompt.com/public/pitrtools
I can't really dispute a recommendation from JD. I'll have to look
into that. It's a shame
As a note, all PITRTools does is wrap around all the tools that you are
trying to make work. So you will still need pg_standby, rsync, ssh
etc...
I have updated the wiki to make it a bit more friendly.
https://projects.commandprompt.com/public/pitrtools/wiki
I've given PITRTools a try,
On Wed, 2009-02-25 at 21:39 +, Thom Brown wrote:
As a note, all PITRTools does is wrap around all the tools
that you are
trying to make work. So you will still need pg_standby, rsync,
ssh
etc...
I have updated the wiki to make
Looks like you didn't run cmd_archiver -C config_file -I
Ahh, okay, that did something, which I think means it created a directory
named after the slave IP in the archive directory. I didn't see any mention
of that switch in the README file, unless it's mentioned elsewhere and I
missed it.
Now
On Wed, 2009-02-25 at 22:06 +, Thom Brown wrote:
Looks like you didn't run cmd_archiver -C config_file -I
Ahh, okay, that did something, which I think means it created a
directory named after the slave IP in the archive directory.
Right that is the queue
Hi all,
We're looking at setting up a warm-standby server using log shipping and
aren't too sure about how we should trigger failover. Is there a
commonly-used approach which is reliable enough to recommend? Looking at
the documentation, there doesn't seem to be any recommendation. I
On Tue, 2009-02-24 at 16:55 +, Thom Brown wrote:
We're looking at setting up a warm-standby server using log shipping
and aren't too sure about how we should trigger failover. Is there a
commonly-used approach which is reliable enough to recommend? Looking
at the documentation, there
13 matches
Mail list logo
