[AnnatarHe]

Summary

Groonga published PGroonga 4.1.0 on 2026-10-09, and its trixie repository now resolves postgresql-18-pgdg-pgroonga to 4.1.0-1. The Dockerfile only accepts the 4.0 line, so every build stops at expected PGroonga 4.0.x, apt resolved 4.1.0-1. That failed the Build check on #3 and the Release run for v1.0.1. v1.0.1 is tagged, but no image was pushed: GHCR still serves only 1.0.0.

This moves PGROONGA_VERSION to 4.1, the latest release, and updates the README and AGENTS.md mentions. The minor-line check stays as it is.

Component versions

Component	Before (1.0.0)	After
PostgreSQL	18.6	newest 18.x at build time (unchanged line)
PostGIS	3.6.4	newest 3.6.x at build time (unchanged line)
PGroonga	4.0.9	4.1.0

The release from this PR is also the first image to include the health-check fix from #3.

Upstream 4.1.0 (release notes):

• Fixes a bug where VACUUM/ANALYZE in another session, before a CREATE INDEX committed, could drop data the new index needs. Searches then failed with "object isn't found" until REINDEX.
• Adds post_filter support to pgroonga_tuple_is_alive(), which matters only to direct pgroonga_command() users.

Upgrade steps for consumers

1. Pull the new release tag and recreate the container on the same volume.
2. Run docker exec -u postgres <container> update-extensions.sh. It runs ALTER EXTENSION pgroonga UPDATE in every database that has PGroonga.
3. If any PGroonga index ever returned "object isn't found", REINDEX it.

Databases without the pgroonga extension need nothing beyond step 1.

Testing

I couldn't build locally (no Docker here). This PR's Build workflow builds the image and runs test/smoke.sh. That covers the PGroonga CJK/English searches in smoke.sql, plus #3's new check that the health check leaves no FATAL in the server log, which hasn't run in CI yet.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-24T12:26:39.303536Z We couldn’t complete this review. Comment @codex review to try again.	3c04b06	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[shelltime]

🤖 Claude Code · Migrate DB image and fix configurable health check

Migrated the remote database deployment to the rawback-app/db 1.0.0 image with 256 MB shared memory, then updated the image repository so its health check uses the configured PostgreSQL user.

💰 Cost	🔢 Tokens	⏱️ Duration	🧠 Model	💬 Prompts	✏️ Lines
$4.50	10.2M	30m (18m active)	claude-opus-5-5	6	+23 / −4

_{10.2M tokens: 130 input · 56.3K output · 10M cache read · 170.7K cache write}

📝 AI summary

Inspected the deployment over ssh rta, produced a migration plan, and carried out steps 1–5 as requested. The database container was switched to the rawback-app/db image pinned at version 1.0.0, with --shm-size=256m added. Work stopped before enabling PGroonga, preserving that as a separate future step.

In a scratch clone of rawback-app/db, updated the Dockerfile HEALTHCHECK so pg_isready runs with -U "${POSTGRES_USER:-postgres}" -d postgres. The smoke test in test/smoke.sh and documentation in README.md and AGENTS.md were also adjusted to cover and explain the health-check behavior. The changes were prepared for the requested upstream PR; no PGroonga enablement or additional follow-up work was performed after the user declined it.

View this session on ShellTime →

_{Updated 2026-10-25 12:26 UTC by ShellTime · totals for the whole session so far · the session page is visible to its owner}