DH_PGXS_TEST(1)

💖 DH_PGXS_TEST(1) 💖

okay bestie, gather round, because this one's from the Debian PostgreSQL infrastructure manual suite and it is so niche but so useful 🫶

---

✨ NAME ✨

dh_pgxs_test — run the testsuite during a PGXS PostgreSQL extension build 🧪🐘

---

🌸 SYNOPSIS 🌸

dh_pgxs_test [loop]

---

🦋 DESCRIPTION 🦋

so here's the tea, bestie ☕ — PostgreSQL extensions have to be installed before you can test them. like, they literally cannot be tested before that happens. which means the normal debhelper way of kicking off tests, the one from dh_auto_test(1), just... does not work here. it's giving ✨incompatible✨.

enter dh_pgxs_test, the main character 👑. it's a dh(1) sequence point created by the pgxs and pgxs_loop debhelper extensions, and it runs after dh_auto_install(1). what does it actually do? it calls pg_buildext installcheck once a PostgreSQL extension module has been built and installed into the debian/packagename/ directory. periodt. 💅

now, if you're the type of person who wants to change the action that dh_pgxs_test calls — and honestly, same — you should call pg_buildext or similar commands yourself. like this:

override_dh_pgxs_test:
        echo "CREATE EXTENSION foo" | pg_buildext psql . . postgresql-%v-foo

look at that. iconic. 🔥

---

🎀 OPTIONS 🎀

• loop — okay so when you do dh --with pgxs, packages get built inside build-%v subdirectories. the loop option is the counterpart to dh --with pgxs_loop and it builds in the top-level directory instead. no cap 🧚

---

🌈 SEE ALSO 🌈

debhelper(7), dh(1), dh_make_pgxs(1), pg_buildext(1). go read them, iykyk 💜

---

💌 AUTHOR 💌

Christoph Berg <myon@debian.org> — tysm for your service 🫡💖

---

okay that's the whole page bestie, you ate that 🍓 this was the Debian PostgreSQL infrastructure manual, version dated 2026-07-28, and yes it really is DH_PGXS_TEST(1) — slay, bye 💅✨🌸