Tom,
>AFAIK this can only happen if you have open transactions in
parallel
>with the VACUUM FULL. Killing off the open transactions should
allow
>the VACUUM to complete. See today's "Still getting VACUUM errors"
>thread over in pgsql-admin.
It is rare since only one batch process open transaction and insert large
objects, and this process is not running at the moment of the vacuum, all
the other accesses are readings with out transactions...
there is some form to know if there are transactions open?
Thanks
Sergio