I'm using 7.1.2 on a Red Hat 7.1 box.
I have a database where the backend crashes when I do "vacuum analyze".
It does not happen when I do pg_dump or vacuum, and other databases on
the same box work fine with vacuum analyze. Here's the tail end of the
"vacuum verbose analyze" log:
NOTICE: Analyzing...
NOTICE: --Relation document--
NOTICE: Pages 15: Changed 0, reaped 0, Empty 0, New 0; Tup 79: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 72, MaxLen 2028; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. CPU 0.00s/0.00u sec.
NOTICE: Index document_pkey: Pages 2; Tuples 79. CPU 0.00s/0.00u sec.
NOTICE: Index document_unique_region_period: Pages 2; Tuples 79. CPU
0.00s/0.00u sec.
NOTICE: --Relation pg_toast_28441--
NOTICE: Pages 59: Changed 0, reaped 1, Empty 0, New 0; Tup 262: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 2, MinLen 76, MaxLen 2034; Re-using:
Free/Avail. Space 4084/0; EndEmpty/Avail. Pages 0/0. CPU 0.00s/0.01u sec.
NOTICE: Index pg_toast_28441_idx: Pages 2; Tuples 262: Deleted 0. CPU
0.00s/0.00u sec.
NOTICE: Analyzing...
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
connection to server was lost
It happens at the same point each time I try it. I haven't noticed any
particular problems using the database, but this (obviously) worries me.
I've already tried dropping the database, recreating it, and re-importing
it from the pg_dump; the same thing happens.
What else should I try?
--
Robert L Mathews, Tiger Technologies