From: Brad Nicholson <bnichols@ca.afilias.info>
To: pgsql-admin@postgresql.org
Subject: Re: replication for hot-standby?
Date: Tue, 05 Jul 2005 11:09:13 -0400
Message-ID: <42CAA299.6000907@ca.afilias.info> (raw)
In-Reply-To: <42ca35fb$0$22442$8fe63b2a@news.disputo.net>
References: <42c54261$0$22444$8fe63b2a@news.disputo.net>
<42C98FF3.80400@ca.afilias.info>
<42ca35fb$0$22442$8fe63b2a@news.disputo.net>
Hannes Dorbath wrote:
> Yes, it does in /some way/, but it's quite hackish and error prone.. :/
It's far from hackish, and only error prone if you don't follow best
practices (ie:fireing DDL changes through slonik without testing them on
_all_ nodes first).
>
>> If there is anything broken about the script, or about how it
>> executes on a particular node, this will cause the slon daemon for
>> that node to panic and crash. If you restart the node, it will, more
>> likely than not, try to repeat the DDL script, which will, almost
>> certainly, fail the second time just as it did the first time.
>
>
>> Unfortunately, this nonetheless implies that the use of the DDL
>> facility is somewhat fragile and fairly dangerous.
>
>
>> If your applications do not have fairly stable SQL schemas, then
>> using Slony-I for replication is likely to be fraught with trouble
>> and frustration.
>
>
> Sorry, this really doesn't sound like something I'd like to use in a
> production environment..
>
It totally depends on your enviornment. We use Slony in a 24x7x365
production enviornment. Usage requires that you know what your doing,
and fair amount of care and planning when using it. But Slony was
never designed with the intent of being a click and forget type system.
If you have environement where the schema is not stable, replicating
with Slony will likely take a lot of work, but can be done safely. If
you don't have control over your schema changes (ie a web hosting
environement where the end user can change the schema), it's certainly
out of the picture. In that scenario, I think you're going to have a
hard time finding a replication engine that will let you have a hot
standyby.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bnichols@ca.afilias.info
Subject: Re: replication for hot-standby?
In-Reply-To: <42CAA299.6000907@ca.afilias.info>
References: <42c54261$0$22444$8fe63b2a@news.disputo.net> <42C98FF3.80400@ca.afilias.info> <42ca35fb$0$22442$8fe63b2a@news.disputo.net> <42CAA299.6000907@ca.afilias.info>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox