| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Casey Duncan <casey(at)pandora(dot)com> |
| Cc: | PostgreSQL-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Where art thou pg_clog? |
| Date: | 2007-02-15 21:46:53 |
| Message-ID: | 20070215214653.GU4682@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Casey Duncan wrote:
> We have a production system with multiple identical database
> instances on the same hardware, with the same configuration, running
> databases with the exact same schema. They each have different data,
> but the database sizes and load patterns are almost exactly the same.
>
> We are running pg 8.1.5 (upgraded the day before 8.1.6 came out, oh
> well ;^) and since then we have noticed the following error on two of
> the servers:
>
> 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
Can you relate it to autovacuum?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2007-02-15 21:49:38 | Re: Database performance comparison paper. |
| Previous Message | Emi Lu | 2007-02-15 21:46:31 | Re: postgresql 8.2 Installation error at "gmake" |