Tatsuo Ishii wrote:
I'm designing a warm-standby Postgres/pgpool system accepting
connections from a number of application servers.
Of course, running a single instance of pgpool introduces a single point
of failure.
To avoid the SPOF, you could use pgpool-HA or whatever Hot/Standby
I have not checked on pgpool-HA but I'm very inrest in checking that
out now since the Ucarp solution that I have right now is on a dev
environment.
Please let us know when that tutorial is live :)
thanks
Marcelo
PostgreSQL DBA
Linux/Solaris System Administrator
http://www.zeroaccess.org
On
Tatsuo,
I also have some online-recory scripts that I have been meaning to
post on the list that perhaps some could use it as another example
together with the ones you currently provide
Marcelo
PostgreSQL DBA
Linux/Solaris System Administrator
http://www.zeroaccess.org
On Dec 13, 2008,
Marcelo,
Great. Please post!
--
Tatsuo Ishii
SRA OSS, Inc. Japan
Tatsuo,
I also have some online-recory scripts that I have been meaning to
post on the list that perhaps some could use it as another example
together with the ones you currently provide
Marcelo
PostgreSQL DBA
Tatsuo Ishii wrote:
Great. Please post!
Attached you'll find mine. They use rsync for the base backup. Heartbeat does
not need any scripts.
I also have some online-recory scripts that I have been meaning to
post on the list that perhaps some could use it as another example
together
Thanks for sharing!
I have similar scripts to copy-base-backup and pgpool-start-remote. I
think I'm not needing pgpool-recovery-pitr. Am I wrong or the pitr one
is in case I don't use a two stages recovery?
Thanks,
Daniel
-Original Message-
From: pgpool-general-boun...@pgfoundry.org
Hi Edward,
Thank you for your interesting script. However this script has better
pgpool-II handling than pgpool-HA's.
Unfortunately I can't merge into pgpool-HA because of license conflict.
Pgpool-HA's is BSD style but yours is GPL...
Here's some remarks.
-I do not recommend to use /etc/init.d
