Skip to content

conf: switch AgensGraph templates to PostgreSQL 18 (AgensGraph 2.18) - #793

Open
skjeong-afk wants to merge 1 commit into
pgsty:mainfrom
skjeong-afk:agens-pg18
Open

skjeong-afk wants to merge 1 commit into
pgsty:mainfrom
skjeong-afk:agens-pg18

Conversation

@skjeong-afk

Copy link
Copy Markdown

Hello, I'm on the AgensGraph team at SKAI Worldwide (formerly Bitnine). Thank you for packaging AgensGraph in Pigsty.

AgensGraph 2.18 is based on PostgreSQL 18, and agensgraph-18 (2.18.6.0) is already published in the Pigsty repo.
However, the templates still set pg_version: 17, so ./configure -c agens installs agensgraph-17 (2.17.0).

This PR switches the AgensGraph templates to PostgreSQL 18:

  • conf/agens.yml: pg_version: 18, header comment
  • conf/demo/kernel.yml: pg_version: 18 for pg-agens
  • conf/README.md: (17) -> (18)

Related items outside this repo, if you have time:

  1. Docs (https://pigsty.io/docs/pgsql/kernel/agensgraph/ and the Chinese page on pigsty.cc) still describe 2.17.0 / PG17.
    The 2.17.0 release notes link (/latest/release_notes/agensgraph_release_notes_2_17_0.html) now returns 404, because /latest/ moved to 2.18.
    Current docs: https://tech.skaiworldwide.com/docs/en/agensgraph/latest/
  2. Packages: AgensGraph 2.18.6.1 was released on 2026-10-28 (https://github.com/skaiworldwide-oss/agensgraph/releases/tag/v2.18.6.1).
    It only fixes the contact address and home page shown by agens --help / ag_ctl --help, with no catalog or on-disk format changes, so it is low priority.

I have not run a full deployment with this change. Happy to help test if useful. Thanks!

🤖 Generated with Claude Code

agensgraph-18 (2.18.6.0) is published in the Pigsty repo, but the
templates still set pg_version: 17 and install agensgraph-17 (2.17.0).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant