Re: pg_amcheck option to install extension - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_amcheck option to install extension
Date
Msg-id YH4xXtcI3lDxo/+P@paquier.xyz
Whole thread Raw
In response to Re: pg_amcheck option to install extension  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_amcheck option to install extension  (Mark Dilger <mark.dilger@enterprisedb.com>)
Re: pg_amcheck option to install extension  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Mon, Apr 19, 2021 at 12:53:29PM -0400, Tom Lane wrote:
> FWIW, I think that putting them both in contrib makes the most
> sense from a structural standpoint.
>
> Either way, though, you'll still need the proposed option to
> let the executable issue a CREATE EXTENSION to get the shlib
> loaded.  Unless somebody is proposing that the extension be
> installed-by-default like plpgsql, and that I am unequivocally
> not for.

Agreed.  Something like src/extensions/ would be a tempting option,
but I don't think that it is a good idea to introduce a new piece of
infrastructure at this stage, so moving both to contrib/ would be the
best balance with the current pieces at hand.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: "Andreas 'ads' Scherbaum"
Date:
Subject: Re: GSoC 2021 Proposal Document
Next
From: Julien Rouhaud
Date:
Subject: Re: Bogus collation version recording in recordMultipleDependencies