Re: pg_upgrade: when the --old-bindir requires "additional" $libdir/ plugins?

From: Pavel Raiskup <praiskup(at)redhat(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_upgrade: when the --old-bindir requires "additional" $libdir/ plugins?
Date: 2018-04-18 14:54:14
Message-ID: 1752296.SLvVdrG800@nb.usersys.redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday, April 18, 2018 4:22:23 PM CEST Tom Lane wrote:
> Pavel Raiskup <praiskup(at)redhat(dot)com> writes:
> > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1557490
>
> There are certainly plenty of reasons why extension .so's might be needed
> during pg_dump, even in a binary-upgrade situation. The first example
> that comes to mind is that an hstore-type constant appearing in a view
> definition would require hstore_out() to be invoked while dumping the view
> definition.

Thanks for the example, Tom. I'll resolve the bug [2] then.

Pavel

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Raiskup 2018-04-18 15:04:19 Re: pg_upgrade: when the --old-bindir requires "additional" $libdir/ plugins?
Previous Message Adrian Klaver 2018-04-18 14:43:01 Re: pg_upgrade: when the --old-bindir requires "additional" $libdir/ plugins?