Re: vacuumdb problem

Marcin Inkielman <marn(at)wsisiz(dot)edu(dot)pl> writes:
> NOTICE: FlushRelationBuffers(osoby, 228): block 223 is referenced
> (private 0, global 1)
> FATAL 1: VACUUM (vc_repair_frag): FlushRelationBuffers returned -2

> this table is referenced in my db by a tree of FOREIGN KEYs.

Hmm, I wonder whether there is a buffer-refcount leak in the foreign
key stuff.

> however my db seems to work and I am able to do pg_dump
> Rescently, I dumped and restored it and for a few days I was able to
> do vacuumdb. Today, the problem is here again.

You will probably find that stopping and restarting the postmaster
will make the problem go away (until it comes back again). Might
be an acceptable workaround to let you vacuum, until we can find
the bug.

Do you think you can extract a reproducible example? Short of that,
it'd be helpful to at least see the declarations of "osoby" and all
associated tables.

regards, tom lane