Re: pain of postgres upgrade with extensions - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: pain of postgres upgrade with extensions
Date
Msg-id 9f2ea73c290cc913675f32e74085e34f@biglumber.com
Whole thread Raw
In response to Re: pain of postgres upgrade with extensions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pain of postgres upgrade with extensions  (Dave Potts <dave.potts@pinan.co.uk>)
Re: pain of postgres upgrade with extensions  (Martijn van Oosterhout <kleptog@svana.org>)
Re: pain of postgres upgrade with extensions  ("Kevin Martins" <martins506@hotmail.com>)
List pgsql-general
-----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....

- --
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-----



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Function Returning SETOF RECORD: Trouble With Char Type
Next
From: Dave Potts
Date:
Subject: Re: pain of postgres upgrade with extensions