Chris Travers wrote:
Carlos Henrique Reimer wrote:
I read some documents about replication and realized that if you plan
on using asynchronous replication, your application should be
designed from the outset with that in mind because asynchronous
replication is not something that can be easily “added on” after the
fact.
Am I right?
Depending on your needs, you may find pgpool and Slony to be a
workable combination. This is better when you have a lot of reads and
only occasional writes. This way writes get redirected back to the
master, and read-only transactions get run on the slaves.
As long as you don't have any functions that write to the db. pgpool
could (and likely would) redirect some of these to the subscriber.
Slony would prevent the data from being written (which would prevent
the subscriber from being corrupted).
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
message can get through to the mailing list cleanly
