From: Jie Liang <jliang@ipinc.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: Re: [SQL] I cannot vacuum
Date: Wed, 21 Mar 2001 13:12:28 -0800 (PST)
Message-ID: <Pine.BSF.4.10.10103211308340.78801-100000@tidal.ipinc.com> (raw)
In-Reply-To: <20756.985135435@sss.pgh.pa.us>
Tom,
NOTICE: --Relation ip--
NOTICE: Pages 4244: Changed 1, reaped 13, Empty 0, New 0; Tup 665627: Vac
32, Keep/VTL 0/0, Crash 0, UnUsed 594, MinLen 48, MaxLen 48; Re-using:
Free/Avail. Space 33168/26016; EndEmpty/Avail. Pages 0/12. CPU 0.32s/2.26u
sec.
NOTICE: Index ip_ip: Pages 3204; Tuples 665627: Deleted 13. CPU
0.20s/0.80u sec.
NOTICE: Index ip_id: Pages 1499; Tuples 665627: Deleted 13. CPU
0.04s/0.81u sec.
NOTICE: Rel ip: Pages: 4244 --> 4240; Tuple(s) moved: 13. CPU 0.00s/0.00u
sec.
NOTICE: Index ip_ip: Pages 3204; Tuples 665627: Deleted 13. CPU
0.19s/0.79u sec.
NOTICE: Index ip_id: Pages 1499; Tuples 665627: Deleted 13. CPU
0.09s/0.74u sec.
NOTICE: FlushRelationBuffers(ip, 4240): block 4242 is referenced (private
0, global 1)
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.
This happen again today,
urldb=# select version();
version
-------------------------------------------------------------------------
PostgreSQL 7.0.0 on i386-unknown-freebsdelf3.4, compiled by gcc 2.7.2.3
Dose later version such as 7.0.3 resolved this problem??
if so, which version I should install?
Jie LIANG
St. Bernard Software
10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873
jliang@ipinc.com
www.stbernard.com
www.ipinc.com
On Tue, 20 Mar 2001, Tom Lane wrote:
> Jie Liang <jliang@ipinc.com> writes:
> > NOTICE: FlushRelationBuffers(ip, 4223): block 4365 is referenced (private
> > 0, global 8)
> > FATAL 1: VACUUM (vc_vacheap): FlushRelationBuffers returned -2
>
> Try restarting your postmaster.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: jliang@ipinc.com, tgl@sss.pgh.pa.us, pgsql-admin@postgresql.org
Subject: Re: [SQL] I cannot vacuum
In-Reply-To: <Pine.BSF.4.10.10103211308340.78801-100000@tidal.ipinc.com>
References: <20756.985135435@sss.pgh.pa.us> <Pine.BSF.4.10.10103211308340.78801-100000@tidal.ipinc.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox