Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA36955 for ; Wed, 1 Dec 1999 11:20:23 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA24772; Wed, 1 Dec 1999 11:19:42 -0500 (EST) To: Dipankar Chakrabarti cc: pgsql-sql@hub.org Subject: Re: [SQL] VACUUM PROBLEM In-reply-to: Your message of Tue, 30 Nov 1999 21:40:39 -0800 (PST) <19991201054039.25304.qmail@web124.yahoomail.com> Date: Wed, 01 Dec 1999 11:19:42 -0500 Message-ID: <24770.944065182@sss.pgh.pa.us> From: Tom Lane Dipankar Chakrabarti writes: > I am having problem while doing vacuum. > The error message is as follows: > NOTICE: Rel queuestatval: Pages: 2 --> 1; Tuple(s) > moved: 16. Elapsed 0/0 sec. > NOTICE: BlowawayRelationBuffers(queuestatval, 1): > block 1 is referenced (private 0, last 0, global 1) > pqReadData() -- backend closed the channel > unexpectedly. This probably means the backend > terminated abnormally before or while processing the > request. If you look in the postmaster log file, you should find additional info about the crash. 6.5.* libpq has a bug that makes it discard the last backend error message if it sees an unexpected channel closure :-(. So there is probably at least one error message that you're not seeing on the client side --- but it should be there in the log file. regards, tom lane