percona / percona/postgres-packaging
pg17 postinst: 111: db_stop: not found
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 12
- Forks
- 15
- Avg merge
- 1h 26m
- Merged PRs (30d)
- 18
Description
When installing percona-postgresql-17 on Ubuntu 24.04, one gets an /var/lib/dpkg/info/percona-postgresql-17.postinst: 111: db_stop: not found error.
Log:
...
Setting up percona-postgresql-17 (2:17.0-1.noble) ...
Creating new PostgreSQL cluster 17/main ...
/usr/lib/postgresql/17/bin/initdb -D /var/lib/postgresql/17/main --auth-local peer --auth-host scram-sha-256 --no-instructions
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /var/lib/postgresql/17/main ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default "max_connections" ... 100
selecting default "shared_buffers" ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
/var/lib/dpkg/info/percona-postgresql-17.postinst: 111: db_stop: not found
...
PS: Wondering, why the bogus debian bloat still gets used. Thought, percona distribution is a clean enterprise ready version ...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Ubuntu 24.04 installation and inspect /var/lib/dpkg/info/percona-postgresql-17.postinst around line 111, using the included setup log as the expected failure context. Trace why db_stop is unavailable during post-installation and verify that installing percona-postgresql-17 completes without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, shell
- Domain
- databases, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100