Re: pg_upgade vs config

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgade vs config
Date: 2016-10-02 16:54:05
Message-ID: 26150.1475427245@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> The biggest issue is this: the upgrade fails completely on
> ltree-plpython and hstore-plpython, presumably because these modules
> rely on the plpython module being loaded first. pg_upgrade rather
> simple-mindedly calls LOAD on the object library to test if it's usable.

FWIW, that seems to have worked fine yesterday on prairiedog.

I suspect the explanation is that macOS's dynamic linker is smart enough
to pull in plpython when one of those modules is LOAD'ed. The ideal fix
would be to make that happen on all platforms. I'm not actually sure
why it doesn't already; surely every dynamic linker in existence has
such a capability.

[ digs more deeply ... ] Oh, weird: it looks like this succeeded in
every case except 9.6->HEAD upgrade. Did we break something recently?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-10-02 17:33:48 Re: pg_upgade vs config
Previous Message Pavel Stehule 2016-10-02 15:42:37 Re: Hash Indexes