From: Scott Marlowe <scott.marlowe@gmail.com>
To: Detlef Rudolph <runic@gmx.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: select count(*) performance
Date: Fri, 17 Aug 2007 20:14:01 -0500
Message-ID: <dcc563d10708171814q64ff79fdx5bd32477f81a1157@mail.gmail.com> (raw)
In-Reply-To: <5i64cvF3mnmcsU1@mid.individual.net>
References: <1186578085.034463.116030@q75g2000hsh.googlegroups.com>
<5i64cvF3mnmcsU1@mid.individual.net>
On 8/11/07, Detlef Rudolph <runic@gmx.de> wrote:
> Hello Group,
>
> I've tried the VACUUM ANALYSE, that doesn't help
> much, but VACUUM FULL improves Performance down
> from about 40 secs to 8.
If vacuum full fixes a performance problem, then you have a regular
vacuum problem of some sort.
Make sure regular vacuum runs often enough and make sure your fsm
settings are high enough to allow it to reclaim all deleted tuples
when it does run.
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: scott.marlowe@gmail.com, runic@gmx.de
Subject: Re: select count(*) performance
In-Reply-To: <dcc563d10708171814q64ff79fdx5bd32477f81a1157@mail.gmail.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