Received: from mailhost.cs.auc.dk (mailhost.cs.auc.dk [130.225.194.2]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2SEf5U65870 for ; Wed, 28 Mar 2001 09:41:06 -0500 (EST) (envelope-from poulc@cs.auc.dk) Received: from borg.cs.auc.dk (poulc@borg.cs.auc.dk [130.225.194.22]) by mailhost.cs.auc.dk (8.9.3/8.9.3) with ESMTP id QAA05925; Wed, 28 Mar 2001 16:40:46 +0200 (MET DST) Date: Wed, 28 Mar 2001 16:40:46 +0200 (MEST) From: "Poul L. Christiansen" To: A James Lewis cc: Graham Vickrage , Postgres SQL Subject: Re: Killing Postmaster In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200103/576 X-Sequence-Number: 2246 A week? That sounds much too long to me (assuming that you have PostgresSQL funning on fairly good hardware). There could be something wrong with at specific table. Try to vacuum a table one at the time using "vacuum verbose MyTable", and report any error you may find. I don't understand the output of a vacuum verbose, but I'm sure other people on this list do :-) Poul L. Christiansen On Wed, 28 Mar 2001, A James Lewis wrote: > > I have a vacuum which has been running for about a week, is that too long? > > On Wed, 28 Mar 2001, Poul L. Christiansen wrote: > > > On Wed, 28 Mar 2001, Graham Vickrage wrote: > > > > > Hi All, > > > > > > What is the correct way of killing postgres 7.0 on redhat linux. > > > > "man pg_ctl". > > > > > > > > Is there a reason why vacuum hangs on a DB with about 1.5 million rows? > > > > Vacuum can take a long time with 1.5M records. How long have you > > waited? Is there any error message? > > > > Poul L. Christiansen > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 4: Don't 'kill -9' the postmaster > > > > A. James Lewis (james@fsck.co.uk) > If your OS needs a virus detector... RUN!!! > ...Out and get Linux! >