| From: | Alan Hodgson <ahodgson(at)simkin(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: DB errors |
| Date: | 2007-10-12 18:03:29 |
| Message-ID: | 200710121103.29226@hal.medialogik.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday 12 October 2007, "Akash Garg" <akash(dot)garg(at)gmail(dot)com> wrote:
> We had a crash of one of our db systems last night. After doing a fsck
> of he file system and getting the db backup, we're getting a lot of these
> messages in our logs. The DB will also occasionally crash now.
>
> Oct 12 07:40:16 postgres[30770]: [3-1] 2007-10-12 07:40:16 PDTERROR:
> could not access status of transaction 2259991368
> Oct 12 07:40:16 postgres[30770]: [3-2] 2007-10-12 07:40:16 PDTDETAIL:
> Could not read from file "pg_clog/086B" at offset 73728: Success.
>
> Any ideas?
>
Restore from backup. And find out why your server doesn't respect fsync.
--
The global consumer economy can best be described as the most efficient way
to convert natural resources into waste.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joao Miguel Ferreira | 2007-10-12 18:13:01 | replicating to a stopped server |
| Previous Message | Relyea, Mike | 2007-10-12 17:59:02 | Re: Out of memory with ODBC |