hi

i have a simple master slave setup.  At some point in the future, i'd 
like to upgrade to postgres 8.0.   For minor dot releases, i would shut 
down slony and postgres, upgrade postgres, rebuild slony against the 
new postgres and restart both, swithover and do the same on the old 
master and swithover again and everything would work fine.

None of these dot upgrades required an initdb/dump/reload.    I am 
hoping that for moving to 8.0 i can do the same, but during the upgrade 
process do a dump/initdb/reload.  Will this approach work, or are their 
strange caveats for things like xid's and oid's?

I can always drop the slave node, upgrade postgres and slony and 
initdb, load schema, and rerun my slony script to add the slave node, 
create the sets and add the tables and sequences, however i don't want 
to use this approach because during the subscription process, there is 
a pretty heavy load put on the master as data is dumped and reloaded.   
Plus, I'll have to do this twice.  Plus, our database is large enough 
that adding a node takes a very very long time.

On a side note, It would be great if we could get a FAQ going on the 
gborg site.   This will probably be a pretty common question over the 
next few months as people upgrade to 8.0.    Christopher has one at 
http://linuxdatabases.info/info/faq.html it seems like it might be 
linked to form the gborg project pages, or just moved there.

--brian

--------------------------------------------
MobyGames
http://www.mobygames.com
The world's largest and most comprehensive?
gaming database project
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1644 bytes
Desc: not available
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050119/f4fb77f9/attachment.bin