pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: pginfo <pginfo@t1.unisoftbg.com>
To: Bill Moran <wmoran@potentialtech.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: slow vacuum performance
Date: Wed, 24 Mar 2004 15:21:32 +0100
Message-ID: <4061996C.E230AF23@t1.unisoftbg.com> (raw)
References: <406160DF.44D0988C@t1.unisoftbg.com>
	<4061961F.6080009@potentialtech.com>

Hi Bill,
I am vacuuming every 24 h.
I have a cron script about i.
But if I make massive update (for example it affects 1 M rows) and I start vacuum,
it take this 2 h.
Also I will note, that this massive update is running in one transaction ( I can
not update 100K and start vacuum after it).

regards,
ivan.

Bill Moran wrote:

> pginfo wrote:
> > Hi,
> >
> > I am running pg 7.4.1 on linux box.
> > I have a midle size DB with many updates and after it I try to run
> > vacuum full analyze.
> > It takes about 2 h.
> > If I try to dump and reload the DB it take 20 min.
> >
> > How can I improve the vacuum full analyze time?
>
> How often are you vacuuming?  If you've gone a LONG time since the last vacuum,
> it can take quite a while, to the point where a dump/restore is faster.
>
> A recent realization that I've had some misconceptions about vacuuming led me
> to re-read section 8.2 of the admin guide (on vacuuming) ... I highly suggest
> a review of these 3 pages of the admin manual, as it contains an excellent
> description of why databases need vacuumed, that one can use to determine how
> often vacuuming is necessary.
>
> --
> Bill Moran
> Potential Technologies
> http://www.potentialtech.com






view thread (12+ messages)  latest in thread

Message-ID: <4061996C.E230AF23@t1.unisoftbg.com>
Permalink:  ../4061996C.E230AF23@t1.unisoftbg.com/
Also on:    postgresql.org/message-id/4061996C.E230AF23@t1.unisoftbg.com

 · 

reply

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pginfo@t1.unisoftbg.com, wmoran@potentialtech.com
  Subject: Re: slow vacuum performance
  In-Reply-To: <4061996C.E230AF23@t1.unisoftbg.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