PG 7.0 vacuum problem

From: Marcin Inkielman <marn(at)wsisiz(dot)edu(dot)pl>
To: pgsql-general(at)postgresql(dot)org
Subject: PG 7.0 vacuum problem
Date: 2000-05-25 23:11:03
Message-ID: Pine.LNX.4.21.0005260102060.32762-100000@mi.marnnet
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

HI!

i rescently upgraded my system from PG6.53 to PG7.0. after a few days of
work i am unable to do a vacuum on one of tables:

nat=# VACUUM verbose analyze osoby;
NOTICE: --Relation osoby--
NOTICE: Pages 189: Changed 0, reaped 24, Empty 0, New 0; Tup 3436: Vac
29, Keep/VTL 0/0, Crash 0, UnUsed 180, MinLen 68, MaxLen
608; Re-using: Free/Avail. Space 67568/4196; EndEmpty/Avail. Pages
7/14. CPU 0.01s/0.95u sec.
NOTICE: Index osoby_Imię_key: Pages 33; Tuples 3436: Deleted 0. CPU
0.00s/0.01u sec.
NOTICE: Index osoby_pkey: Pages 12; Tuples 3436: Deleted 0. CPU
0.00s/0.01u sec.
NOTICE: Rel osoby: Pages: 189 --> 182; Tuple(s) moved: 0. CPU 0.00s/0.00u
sec.
NOTICE: FlushRelationBuffers(osoby, 182): block 186 is referenced
(private 0, global 3)
FATAL 1: VACUUM (vc_repair_frag): FlushRelationBuffers returned -2
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.

everything other (including pg_dump) work fine

any ideas anybody?

do i risk anything if i do:

pg_dump nat> tmp
dropdb nat
createdb nat
psql nat <tmp

???

thanks in advance!

Marcin Inkielman

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-05-25 23:49:00 Re: PG 7.0 vacuum problem
Previous Message Tom Lane 2000-05-25 23:01:16 Re: Limits on PostgreSQL