[RFC on language-extensions]: plperlu / plpython3u extensions, structural fit?

未关闭
  • 哪里不对？
#396 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
go, perl, postgresql, python
领域
databases

调研方向

Start by reading the Extensions Requirements and the existing PostgreSQL language extension implementation to see how extensions are organized into image containers. Compare that structure with the listed plperl and plpython3u package files, then decide whether language and datatype conversion extensions can fit the project’s requirements. Done means the CNPG team has a clear approach for supporting these language extensions.

由索引模型根据 Issue 内容生成。

描述

I am finding myself needing to implement a CNPG installation with plperlu and plpython3u language support.

Based on https://github.com/cloudnative-pg/cloudnative-pg/issues/9487#issuecomment-3669351028 , I believe the preferred canonical solution would be to implement these as extensions-containers shipped extensions.

However, looking at the implementation of the postgres language extensions, I am unsure the Extensions Requirements, as quoted are a good fit.

Namely, the structure of a postgres language extension does not fit the 'one extension per folder' structural requirement, as language extensions actually ship multiple extensions:

  • The language implementation itself
  • Datatype conversion extensions (sample filelist at end)

Given the conflict in extensions-containers' requirements, and how language extensions ship, I think I may be left with going back to building personalized base container images, as I do not think shipping multiple ImagePlugins per language would really be a good idea. What are the CNPG team's thoughts on this sort of situation?

Extension bundling example:

$ dpkg -L postgresql-plperl-18 postgresql-plpython3-18 | grep /usr/share/postgresql/18/extension | grep -vE 'extension$'
/usr/share/postgresql/18/extension/bool_plperl--1.0.sql
/usr/share/postgresql/18/extension/bool_plperl.control
/usr/share/postgresql/18/extension/bool_plperlu--1.0.sql
/usr/share/postgresql/18/extension/bool_plperlu.control
/usr/share/postgresql/18/extension/hstore_plperl--1.0.sql
/usr/share/postgresql/18/extension/hstore_plperl.control
/usr/share/postgresql/18/extension/hstore_plperlu--1.0.sql
/usr/share/postgresql/18/extension/hstore_plperlu.control
/usr/share/postgresql/18/extension/jsonb_plperl--1.0.sql
/usr/share/postgresql/18/extension/jsonb_plperl.control
/usr/share/postgresql/18/extension/jsonb_plperlu--1.0.sql
/usr/share/postgresql/18/extension/jsonb_plperlu.control
/usr/share/postgresql/18/extension/plperl--1.0.sql
/usr/share/postgresql/18/extension/plperl.control
/usr/share/postgresql/18/extension/plperlu--1.0.sql
/usr/share/postgresql/18/extension/plperlu.control
/usr/share/postgresql/18/extension/hstore_plpython3u--1.0.sql
/usr/share/postgresql/18/extension/hstore_plpython3u.control
/usr/share/postgresql/18/extension/jsonb_plpython3u--1.0.sql
/usr/share/postgresql/18/extension/jsonb_plpython3u.control
/usr/share/postgresql/18/extension/ltree_plpython3u--1.0.sql
/usr/share/postgresql/18/extension/ltree_plpython3u.control
/usr/share/postgresql/18/extension/plpython3u--1.0.sql
/usr/share/postgresql/18/extension/plpython3u.control
主要语言
Go
星标
58
派生
43
平均合并
1 天 10 小时
30 天内合并 PR
27

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

cloudnative-pg/postgres-extensions-containers 的其他 Issue

查看 cloudnative-pg/postgres-extensions-containers 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。