On Nov 24, 2006, at 4:59 AM, Jakub Ouhrabka wrote:
DETAIL: Failed on request of size 262143996.
STATEMENT: VACUUM ANALYZE tablename
There are few of them, always the same request size(?) but
different two databases (out of 100+) and few different tables
(pg_listener, pg_statistic and few slony tables). Vacumm analyze is
issued by pg_autovacuum.
We're also seeing strange behavior of listen/notify in possibly
corrupted database: there are notify events being received by
listen process which the process didn't subscribed to. Can this be
connected?
I've done little research in mailing list archives and I found
possible cause: table corruption caused by flaky hardware. Does it
sound about right? Are there any other possible causes?
That can also be caused by setting maintenance_work_mem too high for
what your hardware is capable of, though I agree that given the other
problems it's likely that there is some kind of corruption.
--
Jim Nasby jim@xxxxxxxxx
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
