From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_migrator issue with contrib |
Date: | 2009-06-05 20:19:35 |
Message-ID: | 200906052019.n55KJZR29362@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-06-05 20:26:48 | Re: pg_migrator issue with contrib |
Previous Message | Bruce Momjian | 2009-06-05 20:18:34 | Re: pg_migrator issue with contrib |