From: | Jone C <jonecster(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: slow growing table |
Date: | 2005-06-21 15:05:17 |
Message-ID: | 65569526050621080553350f62@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> 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(at)bigfoot(dot)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(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Yves Vindevogel | 2005-06-21 15:07:54 | Re: Limit clause not using index |
Previous Message | John A Meinel | 2005-06-21 15:01:13 | Re: Do Views execute underlying query everytime ?? |