From: | "Henry - Zen Search SA" <henry(at)zen(dot)co(dot)za> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | "out of balance" result on select from suspected index corruption |
Date: | 2008-06-30 03:47:08 |
Message-ID: | 394c3fd5507c7d0d5391475e8e60b0cc.squirrel@zenmail.co.za |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
PG: 8.2.7 (then upgraded to 8.2.9 to try and resolve with same result)
Linux 2.6.25
Our selects which have run normally for a very long time suddenly started:
- consuming all memory.
- crashing (oom) if the select was run directly.
- producing "out of balance" results in one of the column results if run
from within a function.
In an effort to resolve, I upgraded to 8.2.9, which yielded the same results.
VACUUM [full analyze] on the db or suspect table resulted in same as above.
Eventually, I tried reindexing the table, which also failed as above.
The workaround was to manually drop each index from the offending table,
then re-create them.
The weird "out of balance" message in one of the column results (ie,
instead of 'bob' as a result for that column, it would simply be "out of
balance").
Sorry I can't provide more detail since this happened yesterday as we're
preparing for the month-end billing run (and getting things back online
was critical).... :-(
Regards
Henry
From | Date | Subject | |
---|---|---|---|
Next Message | Jamie Deppeler | 2008-06-30 04:32:21 | Postgresql 8.3 Installer issue |
Previous Message | Pierre Thibaudeau | 2008-06-30 01:33:42 | tsearch strategy for incremental search |