Dear list,

I've been studying Slony for replicating a small OLTP database and feel fai=
rly comfortable with using it in this scenario.

My real question relates to log shipping and its use in the following set u=
p.

We have a number of large spatial databases; they are replicated to allow u=
s to cope with sudden increases in traffic, loss of servers, etc. Let say w=
e have 5 runtime databases with 3 of them in use during the day. =


Updating them all is something of a flail and likely to get worse as we exp=
and.

So I am wondering if log shipping would help. My idea would be to have two =
spatial databases, call them dev and QA, linked by Slony. Content does what=
ever until they are satisfied. The two dbs are in sync and now we go to upd=
ate runtime.

Would it feasable to use log shipping to update the runtimes, first the 2 o=
ut of service and then, probably in the evening when traffic drops, put tho=
se two into production and then use log shipping to update the other now qu=
iet runtimes once we rotate them out of production ?

My thinking is that we could automate almost all of this and save engineers=
 and ops people from ever more manual work, and because of the need to not =
do updates to live databases (slows them down, thrashes cache, etc.) I can'=
t seeing using Slony per se (since updates would need to be asyncronous). U=
pdates tend to be sporadic, at lest once a week but sometimes a lot more of=
ten (daily) and vary in size from small to fairly large (several hundred th=
ousand rows changing in many different tables).

Catcalls, questions, caveats all welcome,

Thanks,

Greg Williamson
Senior DBA
GlobeXplorer LLC, a DigitalGlobe company

Confidentiality Notice: This e-mail message, including any attachments, is =
for the sole use of the intended recipient(s) and may contain confidential =
and privileged information and must be protected in accordance with those p=
rovisions. Any unauthorized review, use, disclosure or distribution is proh=
ibited. If you are not the intended recipient, please contact the sender by=
 reply e-mail and destroy all copies of the original message.

(My corporate masters made me say this.)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070916/=
56dae23c/attachment.htm