Last night during a vacuum full, one of our production 7.4.12 databases threw this warning:
WARNING: FlushRelationBuffers("idxtype26", 6137): block 5752 is referenced (private 0, global 1)
vacuumdb: vacuuming of database "cvdb" failed: ERROR: FlushRelationBuffers returned -2
PANIC: cannot abort transaction 35650725, it was already committed
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
We do use some external C functions that deal with creating indexes and locking tables, but we're pretty confident that
they'relocking correctly. Another bit of information, the database gets restarted before the vacuum process begins.
Is this something that will resolve itself the next time the database gets vacuumed or does it need some kind of
immediateaction? Does the index need reindexed?
Thanks
