From: | "Welty, Richard" <richard(dot)welty(at)bankofamerica(dot)com> |
---|---|
To: | Jeff Davis <jdavis-pgsql(at)empires(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgresql replication |
Date: | 2005-08-24 21:07:53 |
Message-ID: | 7A8D99D6C4AE9347886B31F047F26BD6045C5F@ex2k.bankofamerica.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jeff Davis writes:
>The disadvantages:
one more: if you actually have m tables and n servers, you have
m x n tables in reality, which is pretty miserable scaling behavior.
i should think that rules, triggers, and embedded procedures would
explode in complexity rather rapidly.
i know i wouldn't want to administer one of these if there were a lot
of sites.
>I hope this is helpful. Let me know if there's some reason my plan won't
>work.
look at the solution in pgreplicator. site ids are embedded in the
id columns in the tables, so there only m tables, and a bit less insanity.
richard
(dropping out of this conversation, i'm unsubscribing while on vacation)
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Guo | 2005-08-24 21:12:56 | Re: Start up script for Fedora Core 3 |
Previous Message | Sean Davis | 2005-08-24 20:31:54 | Problem finding libpg.3.dylib on macos X in plperlu procedure |