On Mon, Jan 18, 2016 at 01:10:05PM -0500, Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > On Mon, Jan 11, 2016 at 10:44:42AM -0500, Tom Lane wrote: > >> But it gets worse: a report today in pgsql-general points out that > >> even if you have the two languages in use *in different databases*, > >> pg_upgrade will fail, because pg_upgrade rather overenthusiastically > >> loads every .so mentioned anywhere in the source installation into > >> one session. > > > The fix for that would be for pg_upgrade to change > > check_loadable_libraries() to start a new session for each LOAD command. > > Would you like that done? > > Not necessary anymore, at least not for PL/Python; and that solution > sounds a tad expensive.
Yes, it would certainly be inefficient. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
