BUG #5439: Table crash after CLUSTER command - Mailing list pgsql-bugs

From Stefan Kirchev
Subject BUG #5439: Table crash after CLUSTER command
Date
Msg-id 201004260816.o3Q8GJx6091537@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #5439: Table crash after CLUSTER command  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: BUG #5439: Table crash after CLUSTER command  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      5439
Logged by:          Stefan Kirchev
Email address:      stefan.kirchev@gmail.com
PostgreSQL version: 8.3.3
Operating system:   Linux
Description:        Table crash after CLUSTER command
Details:

Hello,
I order to keep good performance on tables CLUSTER is done regularly on each
table every Sunday. Almost every time we loose a table which must be
recreated afterward. The error yield is:
pnp=# select * from  alcatel_bss_kpi_tmp.cs_hourly_kpi limit 1;
ERROR:  could not open relation 1663/16404/2426042: No such file or
directory
It is obvious the engine fails to replace the old relfilenode with the new
one.
Is it possible to recover the data from the pg_toast?
Is it mandatory to lock manually table with ACCESS EXCLUSIVE option or it is
done by the engine along with the CLUSTER command?
Thank you!

pgsql-bugs by date:

Previous
From: manohar cr
Date:
Subject: Re: pgadmin supports on SLES10.3
Next
From: Scott Mead
Date:
Subject: Re: pgadmin supports on SLES10.3