Re: State of support for back PG branches

>A nice pg_upgrade utility would make a big difference. Clearly an
>in-place upgrade is possible, but maintaining is hard. There are two
>broad ways of running a pg_upgrade project - one that is entirely
>independent of the main codebase and one that puts requirements on the
>main codebase developers ("if you change $foo you provide code to
>translate old $foo to new $foo"). Any feel for the relative difficulty
>of the two approaches? And how much push-back there'd be on the latter?
>  
>
You can do in place upgrades with Slony-I and Mammoth Replicator.

Sincerely,

Joshua D. Drake



>Cheers,
>  Steve
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>  
>


-- 
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/