You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ...
The text was updated successfully, but these errors were encountered:
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:
PS: Wondering, why the bogus debian bloat still gets used. Thought, percona distribution is a clean enterprise ready version ...
The text was updated successfully, but these errors were encountered: