Re: Support "make check" for PGXS extensions

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Support "make check" for PGXS extensions
Date: 2025-03-20 21:31:49
Message-ID: 2a05ba53-ff99-452a-a7de-7810cd9ef340@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2025-03-20 Th 9:06 AM, Peter Eisentraut wrote:
> This is a quick follow-up to the extension_control_path patch.  With
> this little additional patch, you can now run "make check" in
> PGXS-using extensions (instead of having to do make install; make
> installcheck with a running instance).  I think this would be very
> convenient for extension development.
>
> The patch is still rough, probably needs a bit of work to do proper
> escaping, quoting, further testing, and it will probably break if you
> use a different source tree layout.  Maybe with a bit of help we can
> get this robust enough.  Or otherwise, it can at least serve as
> inspiration for what you can implement yourself in your extension's
> makefile.

No support for TAP tests, AFAICT. I guess this is a first step, but TAP
support would be nice.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-03-20 21:37:07 Re: md.c vs elog.c vs smgrreleaseall() in barrier
Previous Message Nathan Bossart 2025-03-20 21:31:33 Re: Disabling vacuum truncate for autovacuum