| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Casey Duncan <casey(at)pandora(dot)com> |
| Subject: | Re: Where art thou pg_clog? |
| Date: | 2007-02-15 21:50:25 |
| Message-ID: | 200702152250.25930.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Casey Duncan wrote:
> 2007-02-15 00:35:03.324 PST ERROR: could not access status of
> transaction 2565134864
> 2007-02-15 00:35:03.325 PST DETAIL: could not open file "pg_clog/
> 098E": No such file or directory
>
> The first time this happened, I chalked it up to some kind of disk
> corruption based on the mailing list archives. So I dumped the
> databases, did a fresh initdb, forced an fsck (these run with a jfs
> data partition and an ext2 wal partition) which found no problems and
> then reloaded the databases.
>
> Now about a week later
Unless you actually executed 2565134864 transactions in that one week,
this is still data corruption.
Check for faulty memory.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Casey Duncan | 2007-02-15 22:04:08 | Re: Where art thou pg_clog? |
| Previous Message | Ron Johnson | 2007-02-15 21:49:38 | Re: Database performance comparison paper. |