David Potts wrote:
> This is not a flame about current or previous release of Postgres.
>
> I have just gone through the awful experience of upgrading from Postgres
> 8.2 to 8.3 with a database that had one of the many Postgres extensions
> included. The problem comes down to the way that Postgres extensions are
> packaged up, each extension tends to define some extension specific
> functions, when you do a dump of the database these functions get include.
> If upgrade from one version of Postgres to another, you take a dump of
> the database, which then needs to be upgrade if there have been any
> changes in the extension. The problem being that there doesn’t seem
> to be a way of dumping the database with out including extension specific
> information.
>
Is this something that wouldn't be fixed by:
- dump 8.2 database
- load dump into 8.3 database
- for each extension, run the 8.2 drop extension script in 8.2's contrib
- for each extension, run the 8.3 install extension script in 8.3's contrib
??
Or is it a matter of easily keeping an inventory of what extension is
installed in what db?
Paul
