database: the PostgreSQL reseed probe needs CONNECT on every database #183
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/keel#183
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found by the LNPP pair test on hw12-br1, 2026-10-16 (keel 0.23.29).
The reseed of a PostgreSQL replica (
keel spec apply --system-only --destroy-local-database) refused:Cause:
PROBE_SQLofkeel/system/dbpgseed.pysumspg_database_size(oid)over every database as the rolerepl.pg_database_size()needs CONNECT on the database, or the rolepg_read_all_stats. An application database withREVOKE CONNECT ... FROM PUBLICstops every reseed.The keel-lnpp check database had that REVOKE. keel-lnpp#2 removes it, so the LNPP images work with keel 0.23.29. Other applications can do the same, so keel must not need CONNECT on every database.
Possible fixes, the least power first:
has_database_privilege(oid, 'CONNECT')is true, and say in the report that the free space check left those databases out.pg_read_all_statstorepl. This gives more read access than the reseed needs.