From: Jone C <jonecster@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: slow growing table
Date: Tue, 21 Jun 2005 08:05:17 -0700
Message-ID: <65569526050621080553350f62@mail.gmail.com> (raw)
In-Reply-To: <20050606171253.GA1655@uio.no>
References: <6556952605060609485c622403@mail.gmail.com>
<20050606170037.GA1177@uio.no>
<20050606171253.GA1655@uio.no>
> On second thought... Does a VACUUM FULL help? If so, you might want to
> increase your FSM settings.
Thank you for the reply, sorry for delay I was on holiday.
I tried that it had no effect. I benchmarked 2x before, peformed
VACUUM FULL on the table in question post inserts, then benchmarked 2x
after. Same results...
Should I try your suggestion on deleting the indexes? This table needs
to be accessible for reads at all times however though...
thank you kindly
On 6/6/05, Steinar H. Gunderson <sgunderson@bigfoot.com> wrote:
> On Mon, Jun 06, 2005 at 07:00:37PM +0200, Steinar H. Gunderson wrote:
> > You might have a problem with index bloat. Could you try REINDEXing the
> > indexes on the table and see if that makes a difference?
>
>
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
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: jonecster@gmail.com
Subject: Re: slow growing table
In-Reply-To: <65569526050621080553350f62@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