Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error.
| От | raghu ram |
|---|---|
| Тема | Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error. |
| Дата | |
| Msg-id | CALnrrJSDMCedy24MW1V10_CvjSYdfARYB0tJi2-bA6C=xKN8GA@mail.gmail.com обсуждение исходный текст |
| Ответ на | DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error. (Olga Vingurt <olgavi@checkpoint.com>) |
| Ответы |
Re: DB fails to start: "Could not read from file
"pg_clog/0003" at offset 212992: No error.
Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error. |
| Список | pgsql-general |
On Mon, Jul 16, 2012 at 5:44 PM, Olga Vingurt <olgavi@checkpoint.com> wrote:
We are using PostgreSQL 8.3 on Windows Server.
The db crashed and now it fails to start up.
The error is:
FATAL: could not access status of transaction 4020264
DETAIL: Could not read from file "pg_clog/0003" at offset 212992: No error.
Additional log from event viewer:
LOG: database system was interrupted; last known up at 2012-07-12 11:35:00 CEST
How can we recover from the current state?
Please perform below steps:
1. Backup the current pg_clog/0003 file in different directory
2. Create a file by assumption of make the uncommitted record as they haven't been committed. command as follows:
dd if=/dev/zero of=<data directory location>/pg_clog/0003 bs=256K count=1
В списке pgsql-general по дате отправления: