From: Babanpreet Singh <bbnpreetsingh@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>, Ross Burton <ross.burton@arm.com>,
Babanpreet Singh <bbnpreetsingh@gmail.com>
Subject: [meta-oe][PATCH 0/3] postgresql: add PGXS extension support and pg_cron
Date: Wed, 11 Nov 2026 20:39:54 +0000 [thread overview]
Message-ID: <20261111203957.7-1-bbnpreetsingh@gmail.com> (raw)
PGXS extensions cannot be cross-built in OE today. Patch 1 makes the
postgresql recipe support that, patch 2 adds a class for extension
recipes and patch 3 adds pg_cron as the first one.
Built for qemux86-64 and qemuarm64 and run in a qemux86-64 image. I
also built pgvector, pgaudit, pg_partman, orafce and hll through the
class to check it is not specific to pg_cron.
Babanpreet Singh (3):
postgresql: make PGXS usable for cross-building extensions
pgxs.bbclass: add class for PostgreSQL extensions
pg-cron: add recipe
meta-oe/classes/pgxs.bbclass | 22 +++++++
.../packagegroups/packagegroup-meta-oe.bb | 1 +
meta-oe/recipes-dbs/pg-cron/pg-cron_1.6.8.bb | 13 ++++
.../recipes-dbs/postgresql/files/pg_config | 43 +++++++++++++
meta-oe/recipes-dbs/postgresql/postgresql.inc | 62 +++++++++++++++++--
5 files changed, 135 insertions(+), 6 deletions(-)
create mode 100644 meta-oe/classes/pgxs.bbclass
create mode 100644 meta-oe/recipes-dbs/pg-cron/pg-cron_1.6.8.bb
create mode 100755 meta-oe/recipes-dbs/postgresql/files/pg_config
--
2.43.0
next reply other threads:[~2026-11-11 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 20:39 Babanpreet Singh [this message]
2026-11-11 20:39 ` [meta-oe][PATCH 1/3] postgresql: make PGXS usable for cross-building extensions Babanpreet Singh
2026-11-11 20:39 ` [meta-oe][PATCH 2/3] pgxs.bbclass: add class for PostgreSQL extensions Babanpreet Singh
2026-11-11 20:39 ` [meta-oe][PATCH 3/3] pg-cron: add recipe Babanpreet Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261111203957.7-1-bbnpreetsingh@gmail.com \
--to=bbnpreetsingh@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox