pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: willmington@gmx.net
To: pgsql-admin@postgresql.org
Subject: VACUUM FULL achieves nothing / Postgres 7.3.2 + RedHat 7.3
Date: 15 Sep 2004 01:33:50 -0700
Message-ID: <e6568d.0409150033.17058ef9@posting.google.com> (raw)

Ladies and gentlemen,

I am running a Postgres 7.3.2 on a Red Hat Linux release 7.3
(Valhalla)
in a multiprocessor (4) environment.

There is a db table in one of the databases containing some 20.000
records updated on a daily basis. When attempting to delete about 4000
deprecated records from it the query ran for almost half an hour and
postmaster occupied 100% CPU, so i decided to cancel it. (Note: select
querys run fine and finish within milliseconds).

In order to reproduce the problem, i copied the above database to my
staging system (same linux, same postgres), and ran a vacuum full
analyze. It finished after 33 minutes. After the vacuum full the
deletion from the 20.000 records table succeeded within 23 ms.

Now, here's the problem:
When running the VACUUM FULL on the live system, it finished after 20
Seconds (without error messages) - and did not change anything.
Performance is still bad, and the delete from xxx where ... still
takes forever.

Additional information:
The applications using the database are java - based and create
persistent connections (from a connection pool) to the postgres
database. These connections  are on autocommit, thus, there should not
be any opened transactions preventing the vacuum full from write -
locking the tables.

Any idea what i am doing wrong? Any help appreciated.

Kind regards,

R. Willmington



view thread (5+ messages)  latest in thread

Message-ID: <e6568d.0409150033.17058ef9@posting.google.com>
Permalink:  ../e6568d.0409150033.17058ef9@posting.google.com/
Also on:    postgresql.org/message-id/e6568d.0409150033.17058ef9@posting.google.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: willmington@gmx.net
  Subject: Re: VACUUM FULL achieves nothing / Postgres 7.3.2 + RedHat 7.3
  In-Reply-To: <e6568d.0409150033.17058ef9@posting.google.com>
  References: <e6568d.0409150033.17058ef9@posting.google.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