From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | vtvkerala(at)gmail(dot)com |
Subject: | BUG #15742: Postgres Service is not starting after Windows abrupt Shutdown |
Date: | 2019-04-09 05:32:53 |
Message-ID: | 15742-44be3adfcd833cb8@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15742
Logged by: vinod viswanath
Email address: vtvkerala(at)gmail(dot)com
PostgreSQL version: 9.6.7
Operating system: Microsoft Windows Server 2016 Standard
Description:
Due to a sudden power down, our PostGres server machine shut down
abruptly.
After rebooting, I tried to restart postgres and I get this error:
2019-04-03 14:06:05 IST FATAL: the database system is starting up
2019-04-03 14:06:06 IST FATAL: the database system is starting up
2019-04-03 14:06:40 IST LOG: database system was not properly shut down;
automatic recovery in progress
2019-04-03 14:06:40 IST LOG: redo starts at A/5212A808
2019-04-03 14:06:57 IST LOG: invalid record length at A/52C87C68: wanted
24, got 0
2019-04-03 14:06:57 IST LOG: redo done at A/52C87C40
2019-04-03 14:06:57 IST LOG: last completed transaction was at log time
2019-04-03 13:58:49.502286+05:30
2019-04-03 14:06:58 IST LOG: MultiXact member wraparound protections are
now enabled
2019-04-03 14:06:58 IST LOG: database system is ready to accept
connections
Is there any permanent solution for this, We are able to start the service
after killing the postgres exes from task manager..
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-04-09 06:54:50 | Re: BUG #15742: Postgres Service is not starting after Windows abrupt Shutdown |
Previous Message | Amit Langote | 2019-04-09 04:55:22 | Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed |