Re: List of all* PostgreSQL EXTENSIONs in the world

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: "Joel Jacobson" <joel(at)compiler(dot)org>, "Noah Misch" <noah(at)leadboat(dot)com>, "Joe Conway" <mail(at)joeconway(dot)com>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: List of all* PostgreSQL EXTENSIONs in the world
Date: 2022-02-23 14:33:31
Message-ID: 4b42d465-5edd-434f-8041-94e3189b897a@www.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 23, 2022, at 6:00 AM, Joel Jacobson wrote:
> On Fri, Feb 11, 2022, at 04:46, Noah Misch wrote:
> > How did you make the list? (I'd imagine doing it by searching for
> > repositories containing evidence like \bpgxs\b matches.)
>
> Searching Github for repos with a *.control file in the root dir and a Makefile containing ^PGXS
Interesting. What's an extension? It is something that contains user-defined
objects. It would be good if your list was expanded to contain addons (modules)
that are basically plugins that don't create additional objects in the database
e.g. an output plugin or a module that uses any hooks (such as auth_delay).
They generally don't provide control file (for example, wal2json). I don't know
if can only rely on PGXS check because there are client programs that uses the
PGXS infrastructure to build it.

> Hmm, now that you say it, maybe the ^PGXS regex should be case-insensitive,
> if pgxs can be written in e.g. lower case?
Makefile variable names are case-sensitive. You cannot write pgxs or PgXs; it
should be PGXS.

--
Euler Taveira
EDB https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2022-02-23 14:37:57 Re: List of all* PostgreSQL EXTENSIONs in the world
Previous Message Andrew Dunstan 2022-02-23 14:23:36 Re: List of all* PostgreSQL EXTENSIONs in the world