From: Antoine <melser.anton@gmail.com>
To: Andreas Pflug <pgadmin@pse-consulting.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: n00b autovacuum question
Date: Sun, 19 Mar 2006 13:27:29 +0100
Message-ID: <92d3a4950603190427m47f5fad6k@mail.gmail.com> (raw)
In-Reply-To: <441C4758.9000205@pse-consulting.de>
References: <92d3a4950603180401p7deb391cp@mail.gmail.com>
<441C4758.9000205@pse-consulting.de>
On 18/03/06, Andreas Pflug <pgadmin@pse-consulting.de> wrote:
> Antoine wrote:
> > Hi,
> > I have enabled the autovacuum daemon, but occasionally still get a
> > message telling me I need to run vacuum when I access a table in
> > pgadmin.
>
> pgAdmin notices a discrepancy between real rowcount and estimated
> rowcount and thus suggests to run vacuum/analyze; it won't examine
> autovacuum rules so it might warn although autovac is running ok.
>
> If you're sure autovacuum is running fine, just dismiss the message.
I guess that is my problem - I a not sure it is running fine. The
process is definitely running but I am getting lots of complaints
about performance. This probably has lots to do with crap code and not
much to do with the database but I am still searching the maintenance
avenue... We have a massive project coming up and I want to go for
Postgres (the boss wants Oracle). If I can't get my stuff together I
am not sure my arguments will stick... problem is I don't really have
the time to experiment properly.
Cheers
Antoine
--
This is where I should put some witty comment.
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: melser.anton@gmail.com, pgadmin@pse-consulting.de
Subject: Re: n00b autovacuum question
In-Reply-To: <92d3a4950603190427m47f5fad6k@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