Re: VACUUM FULL produce warnings

spied@yandex.ru writes:
> look please http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253295

I wouldn't worry about it.  It's probably due to the fact that we tend
to release write lock on system catalogs immediately after updating the
catalog, instead of holding the lock till commit.  That means it's
possible for VACUUM FULL to see uncommitted tuples in system catalogs,
which it should never do in user tables.

(This theory does assume that you are making system catalog changes
concurrently with running VACUUM, which doesn't entirely square with
your statement that database updates are "rare".  Perhaps you create
and delete temp tables frequently?)

            regards, tom lane