Re: pg_migrator issue with contrib - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_migrator issue with contrib
Date
Msg-id 200906052019.n55KJZR29362@momjian.us
Whole thread Raw
In response to Re: pg_migrator issue with contrib  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_migrator issue with contrib  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Brad Nicholson wrote:
> >> At the very least, a mention in the documentation of incompatible
> >> contrib module(s) would be nice.  Even better would be a sanity check
> >> added to prevent this.
> 
> > OK, I am looking to the hackers group for recommentations on this.
> 
> One thing I was going to suggest is that pg_migrator check that all the
> .so's in the old installation also exist in the new one.  However that
> could be overkill since you don't know for sure if the old .so is
> referenced anywhere in the database.

Or in this case that the new *.so has the same functions.

> As for the specific problem at hand, it might've been a mistake to
> replace dblink_current_query() with a SQL function instead of changing
> the internal implementation of the C function.  We could still fix that.

I am afraid /contrib is going to be a mine field for this type of
problem so I am going to recommend uninstaling the /contrib module if
possible and retry the migration.  That should work in this case.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_migrator issue with contrib
Next
From: "J. Greg Davidson"
Date:
Subject: blocking referencing system catalogs in 8.4 breaks my code