From: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
---|---|
To: | Brendan Jurd <direvus(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Request for replication advice |
Date: | 2006-11-10 19:51:09 |
Message-ID: | 1163188269.5789.29.camel@dba5.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, 2006-11-11 at 06:34 +1100, Brendan Jurd wrote:
> So, my question for the list is: is Slony + log shipping the direction
> I should be investigating, or is there something else out that I ought
> to consider? My understanding of WAL-based replication is that the
This is certainly the direction to look at. The speed of which
replication keeps on on a log shipped node is going to depend on the
frequency of inserts/updates/deletes, you class of hardware and network
connectivity.
You also need to be absolutely certain that long running queries and
'idle in transaction' transactions are minimized as much as possible (or
completely eliminated). Anything that prevents vacuums from doing there
job properly is going to hurt a slony replica.
Oh, and regarding log shipping itself, I recommend waiting for the
release of 1.1.6 or 1.2.1, there is a fairly serious bug in the current
version that causes log shipping to fall over if you have more than 2
nodes in your config (not just log shipped nodes).
If you have more questions, please sign up for the Slony list.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-11-10 20:07:50 | Re: Request for replication advice |
Previous Message | Jeff Davis | 2006-11-10 19:41:43 | Re: Using GIN indexes on 8.2 |