Re: PG 13 trusted extensions and pg_available_extensions - Mailing list pgsql-general

From Julien Rouhaud
Subject Re: PG 13 trusted extensions and pg_available_extensions
Date
Msg-id CAOBaU_aapS0Fh59_0Y5_fFLS-5BM=MODWyD6w0Akh77YZktimQ@mail.gmail.com
Whole thread Raw
In response to Re: PG 13 trusted extensions and pg_available_extensions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Sat, Sep 26, 2020 at 10:11 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Julien Rouhaud <rjuju123@gmail.com> writes:
> > So, apparently pg_available_extension_versions already had those
> > fields so all the required infrastructure was already there.  I just
> > added the exact same fields to pg_available_extensions, see attached
> > patch.
>
> The reason that pg_available_extensions has only the fields it has
> is that these other values are potentially extension-version-dependent.
> I do not think we can accept this patch.

Oh, I didn't know there could be multiple control files per extension,
and I missed the "aux" reference.  So indeed this patch is
unacceptable.



pgsql-general by date:

Previous
From: Paul Förster
Date:
Subject: Re: pg_upgrade Python version issue on openSUSE
Next
From: Paul Förster
Date:
Subject: Re: pg_upgrade Python version issue on openSUSE