From: Bruno Wolff III <bruno@wolff.to>
To: Bahadur Singh <bahadursingh@yahoo.com>
Cc: pgsql-bugs@postgresql.org
Cc: pgsql-novice@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: BUG #1697: Select getting slower on continously updating data
Date: Fri, 3 Jun 2005 09:49:51 -0500
Message-ID: <20050603144951.GA10195@wolff.to> (raw)
In-Reply-To: <20050603070900.62046.qmail@web50805.mail.yahoo.com>
References: <20050602130259.GB9716@wolff.to>
<20050603070900.62046.qmail@web50805.mail.yahoo.com>
On Fri, Jun 03, 2005 at 00:09:00 -0700,
Bahadur Singh <bahadursingh@yahoo.com> wrote:
>
> Many thanks for this tip !
> But is this good idea to analyse/vacuuming the
> database tables while updates are taking place..
> Since, I update continuously say (100,000 ) times or
> more the same data set.
>
> This is the result of analyze command.
>
> INFO: analyzing "public.salesarticle"
> INFO: "salesarticle": scanned 3000 of 20850 pages,
> containing 62 live rows and 134938 dead rows; 62 rows
> in sample, 431 estimated total rows
>
> Gesamtlaufzeit der Abfrage: 5531 ms.
> Total Time Taken : 5531 ms.
>
> Can you suggest me some clever way to so, because I
> would prefer to do vaccumming while database is not
> loaded with queries/transactions.
While that may be a nice preference, under your usage pattern that does
not appear to be a good idea. As long as your disk I/O isn't saturated
you want to be running vacuums a lot more often than you are. (Analyze should
only be needed if the distrution of values is changing constantly. An example
would be timestamps indicating when an update occured.)
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: bruno@wolff.to, bahadursingh@yahoo.com, pgsql-bugs@postgresql.org, pgsql-novice@postgresql.org
Subject: Re: BUG #1697: Select getting slower on continously updating data
In-Reply-To: <20050603144951.GA10195@wolff.to>
* 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