Re: pain of postgres upgrade with extensions

Greg Sabino Mullane wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
>
>> - dump version N database
>> - create empty version N+1 database
>> - install N+1's version of each needed contrib module into new database
>> - restore dump, ignoring "object already exists" errors
>>
>> There is a TODO to figure out some cleaner way of handling this sort
>> of thing ...
>>
>
> I think I smell a GSOC project....
>

I think there  is a slight misunderstanding here,  I was refering to
extensions items such as postgis, plr, pgperl, etc.  These have a slight
different foot print to the projects in the contrib directory.

Dave
> - --
> Greg Sabino Mullane greg@turnstep.com
> End Point Corporation
> PGP Key: 0x14964AC8 200803121533
> http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
> -----BEGIN PGP SIGNATURE-----
>
> iEYEAREDAAYFAkfYMBMACgkQvJuQZxSWSsjmmwCg1JvB0G2py5jSbJdSZpWR8YyV
> D4YAoLg2ZinEEGoNEU7S2mcL3bqhmNIh
> =7pvA
> -----END PGP SIGNATURE-----
>
>
>
>