Re: pg_amcheck option to install extension
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Mark Dilger <mark.dilger@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-04-20T01:41:50Z
Lists: 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
Commits
-
Provide pg_amcheck with an --install-missing option
- b859d94c6389 14.0 landed