Re: pg_upgrade libraries check
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-05-29T21:35:18Z
Lists: 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