On Dec 27, 2007 12:37 PM, Andrew Sullivan <
ajs@crankycanuck.ca> wrote:
On Thu, Dec 27, 2007 at 10:49:10AM -0500, Josh Harrison wrote:
> Hi,
> We are trying to use slony and WAL shipping for warm standby for replication
It's unusual to use both. Any reason you want to?
We wanted to have 1 master and 1 slave that can be queried and 1 warm standby server that can be brought up in case of crash. So I thought it might be better to have WAL shipping for warm standby since thats working pretty good and Slony for master-slave replication.
Let me know your comments on this setup? What is better for this setup?
Anyway. . .
> What are the other large 24x7 productions systems that use slony and the
> other WAL archiving of postgresql successfully?
Slony was originally written by Jan Wieck, and released by Afilias
(disclosure: currently my employer). Afilias wrote it because we needed
better replication, and there were no community-offered systems. We run the
registries for several Internet top-level domains, including .info and .org.
We have fairly stringent uptime guarantees, and reasonably high transaction
volumes. The databases are not immense, however. Nevertheless, all the DNS
changes for .org (for instance) today are dependent on Slony operating
correctly. I wouldn't say the system is perfect, but I think I can safely
say we've been quite happy with its flexibility. User-space tools are a
little, uh, geeky still (with the possible exception of the GUI support --
our system deployment makes that a little hard for us to use).
There is someone who is using Slony to operate some rather large databases;
he can post here if he wants to share his experience with you.
That will be very useful since our people are debating on the reliability of Slony for large databases!!!
Thanks
Josh