-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
🐛 [PostgresSQL] does not get shutdown properly when stopping the addon #1652
Comments
Hi, thanks for reporting I had noticed that but given there was no visible impact I didn't follow up. Looks like docker-library/postgres#544 I wonder if it's possible to use those levers within the homeassistant's limitations |
Mhh interesting! I was just wondering if not properly shutting the database down could increase the likelihood of database corruptions. |
I will implement their solution it actually seems easy please tell me how it goes ! |
I've pushed version 15.6 (and above) with a potential fix |
Did not work, I'll try something else the script does not capture sigterm as not PID 1 |
Argh I can't find how to pass SIGTERM to the script ;-) |
All good now on version -3 |
Noice thank you! |
Not sure if this is a new issue but I now see |
Ah no it's normal just ensuring pgvecto.rs is enabled |
Hi error came back solving #1654. I'll find something |
Ok, version -4 is good! |
Description
Hi!
Every time I start the database I get this log.
database system was not properly shut down; automatic recovery in progress
Is there no way to properly stop the PostgresSQL server before stopping the addon?
Best,
Paul
Reproduction steps
Addon Logs
Architecture
aarch64
OS
HAos
The text was updated successfully, but these errors were encountered: