From: Jeffrey Baker <jwbaker@gmail.com>
To: Subbiah Stalin-XCGF84 <SSubbiah@motorola.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Update performance degrades over time
Date: Thu, 15 May 2008 09:56:24 -0400
Message-ID: <fd145f7d0805150656n4c0a61aes810b12d72ea3765a@mail.gmail.com> (raw)
In-Reply-To: <BF8D37611DA14544B3A47B8FF055944602759217@ct11exm61.ds.mot.com>
References: <BF8D37611DA14544B3A47B8FF055944602759217@ct11exm61.ds.mot.com>
On Wed, May 14, 2008 at 6:31 PM, Subbiah Stalin-XCGF84
<SSubbiah@motorola.com> wrote:
> Hi All,
>
> We are doing some load tests with our application running postgres 8.2.4. At
> times we see updates on a table taking longer (around
> 11-16secs) than expected sub-second response time. The table in question is
> getting updated constantly through the load tests. In checking the table
> size including indexes, they seem to be bloated got it confirmed after
> recreating it (stats below). We have autovacuum enabled with default
> parameters. I thought autovaccum would avoid bloating issues but looks like
> its not aggressive enough. Wondering if table/index bloating is causing
> update slowness in over a period of time. Any ideas how to troubleshoot this
> further.
Sometimes it is necessary to not only VACUUM, but also REINDEX. If
your update changes an indexed column to a new, distinct value, you
can easily get index bloat.
Also, you should check to see if you have any old, open transactions
on the same instance. If you do, it's possible that VACUUM will have
no beneficial effect.
-jwb
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: jwbaker@gmail.com, SSubbiah@motorola.com
Subject: Re: Update performance degrades over time
In-Reply-To: <fd145f7d0805150656n4c0a61aes810b12d72ea3765a@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