Re: Killing Postmaster

From: "Poul L(dot) Christiansen" <poulc(at)cs(dot)auc(dot)dk>
To: A James Lewis <james(at)fsck(dot)co(dot)uk>
Cc: Graham Vickrage <graham(at)digitalplanit(dot)com>, Postgres SQL <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Killing Postmaster
Date: 2001-03-28 14:40:46
Message-ID: Pine.GSO.4.21.0103281629040.29922-100000@borg.cs.auc.dk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)fsck(dot)co(dot)uk)
> If your OS needs a virus detector... RUN!!!
> ...Out and get Linux!
>

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message A James Lewis 2001-03-28 15:06:13 Re: Killing Postmaster
Previous Message A James Lewis 2001-03-28 14:23:32 Re: Killing Postmaster