Re: pg_upgrade libraries check - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_upgrade libraries check
Date
Msg-id 29612.1338327318@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade libraries check  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade libraries check
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> The bottom line is that already needed function shared objects checking,
> so we just wrapped languages into that as well.

Well, that'd be fine if it actually *worked*, but as per this
discussion, it doesn't work; you have to kluge around the fact that
the shared library name changed.  I'm suggesting that pg_upgrade needs
to be revised to treat this stuff at a higher level.  Yeah, you need to
look at shared library names for bare C functions, but we should be
getting away from that wherever there is a higher-level construct such
as an extension or PL.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Performance patch for Win32
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade libraries check