Thank you for a reply, everybody.
On Mon, Jun 14, 2010 at 11:28 AM, Shinji Nakajima sina...@jops.co.jp
wrote:
PostgreSQL version: 8.3.8
Description: missing chunk number 0 for toast value X in
pg_toast_X
I delete a record, and the system restores, but prime cause is
中嶋 信二sina...@jops.co.jp wrote:
postgres is duplicated.
Red Hat Cluster Suite watches a process of each service.
PGDATA shares it in strage.
There is the thing that a wait server started.
A cluster began the change disposal of servers.
Because A cluster judged a state of postgres to be
The following bug has been logged online:
Bug reference: 5507
Logged by: Shinji Nakajima
Email address: sina...@jops.co.jp
PostgreSQL version: 8.3.8
Operating system: Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Description:missing chunk number 0 for toast
Shinji Nakajima sina...@jops.co.jp writes:
Error message called missing chunk number occurred when I did select of
the specific column of the specific table.
This might indicate that the toast table's index was corrupted.
I delete a record, and the system restores, but prime cause is unknown.
Shinji Nakajima sina...@jops.co.jp wrote:
Error message called missing chunk number occurred when I did
select of the specific column of the specific table.
I delete a record, and the system restores, but prime cause is
unknown. Will this be a bug of the databases?
Errors like this are
