Re: Include extension path on pg_available_extensions - Mailing list pgsql-hackers

From Matheus Alcantara
Subject Re: Include extension path on pg_available_extensions
Date
Msg-id DE1PVW3JOK3K.I4RXDSRSHBVR@gmail.com
Whole thread Raw
In response to Include extension path on pg_available_extensions  ("Matheus Alcantara" <matheusssilv97@gmail.com>)
List pgsql-hackers
Thanks for reviewing this!

On Sun Nov 2, 2025 at 12:11 PM -03, Michael Banck wrote:
> On Mon, Sep 15, 2025 at 09:18:25PM -0300, Matheus Alcantara wrote:
>> postgres=# select * from pg_available_extensions;
>>   name   | default_version | installed_version |                     comment                      |
location
>>
---------+-----------------+-------------------+--------------------------------------------------+---------------------------------------------------
>>  envvar  | 1.0.0           |                   | Get the value of a server environment variable   |
/usr/local/my/extensions/share/postgresql/extension
>>  amcheck | 1.5             |                   | functions for verifying relation integrity       | $system
>>  bloom   | 1.0             |                   | bloom access method - signature file based index | $system
>
> I am not sure just adding the column at the end is best, I would have
> put it before comment so that stays last, maybe somebody else has some
> bikeshedding input here?
>
Yeah, I think that it looks better to keep the comment at the end. If no
objections I'll swap the order of "comment" and "location" columns on
the next version.

--
Matheus Alcantara
EDB: http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Calling PGReserveSemaphores() from CreateOrAttachShmemStructs
Next
From: Andres Freund
Date:
Subject: Missing calls to UnlockBuffers() - unify error handling?