Thread: Vacuum Crash

PostgreSQL 6.3.2 said:

NOTICE:  BlowawayRelationBuffers(places, 322): block 336 is referenced
(private 0, last 0, global 1)
FATAL 1:  VACUUM (vc_rpfheap): BlowawayRelationBuffers returned -2

And now I need to go find the vacuum lock file and blow it away, but I
don't really understand the above message, so wanna ask if I need to worry
about it...

-- "TANSTAAFL" Rich lynch@cognitivearts.com   webmaster@  and www. all of:
R&B/jazz/blues/rock - jademaze.com      music industry org - chatmusic.com
acoustic/funk/world-beat - astrakelly.com   sculptures - olivierledoux.com
my own nascent company - l-i-e.com   cool coffeehouse - uncommonground.com

Richard Lynch wrote:
>
> PostgreSQL 6.3.2 said:
>
> NOTICE:  BlowawayRelationBuffers(places, 322): block 336 is referenced
> (private 0, last 0, global 1)
> FATAL 1:  VACUUM (vc_rpfheap): BlowawayRelationBuffers returned -2
>
> And now I need to go find the vacuum lock file and blow it away, but I
> don't really understand the above message, so wanna ask if I need to worry
> about it...

Restart postmaster, remove pg_vlock file and run vacuum again.

Vadim

Using pg_dump with 6.5b1 on solaris sparc, crashes with a core dump.

This means I can't keep backups and I can't upgrade my data model without
being able to export the old data.

If one of the developers wants debug info let me know what you need (e.g.,
what commands to run in gdb--though I'll have to install this or get run
permissions from the sysadmin).

-- Ari Halberstadt mailto:ari@shore.net <http://www.magiccookie.com/>
PGP public key available at <http://www.magiccookie.com/pgpkey.txt>