-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/etc/postgresql/15/main/pg_hba.conf: No such file or directory #11
Comments
Hi @kwent, it looks like the database isn't being set up (the output is missing the following):
However, I'm not sure how to reproduce (CI logs). |
It looks like something with the latest runner image, as it passes with |
@kwent If possible, try specifying Ubuntu 22.04 instead of the latest (24.04). Not sure what 20250223.1.1 broke but Ubuntu 22.04 works fine with postgresql 15. If keeping to ubuntu-latest, try bumping postgresql to 16. |
Got same issue with postgres 13, |
PostgreSQL post scripts have changed recently. https://salsa.debian.org/postgresql/postgresql-common/-/commit/d9139f7777a42a39b5b6fabbffc9f020fad4dce5 The new database won't be initialized if any other database already exists. Since the runner image comes with PostgreSQL 14 by default, the new version won't automatically trigger You can delete the PostgreSQL 14 cluster just before installing the new version. pg_dropcluster 14 main --stop It will initialize a new database when you install the new version. |
Great find, big thanks @enescakir! The setup script already drops the cluster, but looks like this change is causing it: # Skip if this isn't the newest major installed (assumes other packages are
# unpacked first before this one is configured)
[ "$(ls -v /usr/lib/postgresql/*/bin/postgres | tail -n1)" = "/usr/lib/postgresql/$VERSION/bin/postgres" ] || return 0 Seems like we need to completely remove the previous installation (or set up the new cluster manually). |
Pushed a fix in the commit above. Thanks everyone! |
@ankane @enescakir Thank you! Works great. |
This began to fail as this morning. Any ideas ?
The text was updated successfully, but these errors were encountered: