Re: Killing Postmaster - Mailing list pgsql-sql

From Poul L. Christiansen
Subject Re: Killing Postmaster
Date
Msg-id Pine.GSO.4.21.0103281629040.29922-100000@borg.cs.auc.dk
Whole thread Raw
In response to Killing Postmaster  ("Graham Vickrage" <graham@digitalplanit.com>)
Responses Re: Killing Postmaster
List pgsql-sql
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!
> 



pgsql-sql by date:

Previous
From: "Poul L. Christiansen"
Date:
Subject: Re: Killing Postmaster
Next
From: Dirk Lutzebaeck
Date:
Subject: counting distinct rows on more than one column