From: | Jie Liang <jliang(at)ipinc(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | I cannot vacuum |
Date: | 2001-03-21 00:03:17 |
Message-ID: | Pine.BSF.4.10.10103201559360.78801-100000@tidal.ipinc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-sql |
Hi,
I have a problem today when I vacuum one table which is vacuumed every
today, I tried re_create index also, didn't work.
urldb=# VACUUM VERBOSE ANALYZE id;
NOTICE: Vacuum: table not found
VACUUM
urldb=# VACUUM VERBOSE ANALYZE ip;
NOTICE: --Relation ip--
NOTICE: Pages 4373: Changed 0, reaped 151, Empty 0, New 0; Tup 662929:
Vac 164, Keep/VTL 0/0, Crash 0, UnUsed 23401, MinLen 48, MaxLen 48;
Re-using: Free/Avail. Space 1137624/0; EndEmpty/Avail. Pages 150/0. CPU
0.33s/2.28u sec.
NOTICE: Index ip_ip: Pages 2093; Tuples 662929: Deleted 0. CPU
0.15s/0.73u sec.
NOTICE: Index ip_id: Pages 1311; Tuples 662929: Deleted 0. CPU
0.11s/0.70u sec.
NOTICE: Rel ip: Pages: 4373 --> 4223.
NOTICE: FlushRelationBuffers(ip, 4223): block 4365 is referenced (private
0, global 8)
FATAL 1: VACUUM (vc_vacheap): 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.
any suggestion??
Jie LIANG
St. Bernard Software
10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873
jliang(at)ipinc(dot)com
www.stbernard.com
www.ipinc.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-21 00:43:55 | Re: [SQL] I cannot vacuum |
Previous Message | Bruce Momjian | 2001-03-20 21:19:20 | Re: Re: Use of the LIMIT clause ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-21 00:43:55 | Re: [SQL] I cannot vacuum |
Previous Message | Peter Morgan | 2001-03-20 23:07:22 | Toggle a Bit type ie not field |