From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Pavel Raiskup <praiskup(at)redhat(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_upgrade: when the --old-bindir requires "additional" $libdir/ plugins? |
Date: | 2018-04-18 15:25:45 |
Message-ID: | baeb43b9-87d4-3ad6-7486-7d25bd731167@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/18/2018 08:04 AM, Pavel Raiskup wrote:
> On Wednesday, April 18, 2018 4:43:01 PM CEST Adrian Klaver wrote:
>> I am obviously missing something. If the old server was using hstore in
>> a database how could hstore.so could be accessible to it but not pg_dump?
>
> Because on Fedora we usually run pg_upgrade after distribution upgrade
> (e.g. for Fedora 27 => Fedora 28 upgrade it means also upgrade from PostgreSQL
> 9.6 to 10), and then we provide the old server in different package
> (postgresql-upgrade) which has limited feature set (including the missing
> hstore.so module).
Thanks, now it makes sense.
>
> Pavel
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Vitaliy Garnashevich | 2018-04-18 16:01:44 | Re: Tricking the optimizer |
Previous Message | Pavel Raiskup | 2018-04-18 15:04:19 | Re: pg_upgrade: when the --old-bindir requires "additional" $libdir/ plugins? |