Message-ID: <52DE33B7.7020106@catalyst.net.nz>
Date: Tue, 21 Jan 2014 21:45:43 +1300
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Katharina Koobs <katharina.koobs@uni-konstanz.de>,
 pgsql-performance@postgresql.org
Subject: Re: Increasing query time after updates
References: <000001cf1671$c5e023b0$51a06b10$@uni-konstanz.de>
 <52DE2A97.60002@vmware.com> <001701cf1684$151fbf50$3f5f3df0$@uni-konstanz.de>
In-Reply-To: <001701cf1684$151fbf50$3f5f3df0$@uni-konstanz.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 21/01/14 21:37, Katharina Koobs wrote:
> Dear Heikki,
> thank you for your valuable feedback. Regarding your questions: It
> gradually slower every day. The database size is increasing only
> slightly over time.
>
> I will try your hint regarding CLUSTERING. The difference in effect of
> VACUUM FULL in version 9.0 sounds very interesting. I will discuss the
> update to version 9.0 with my colleague.
>
> Any further idea or feedback is much appreciated.
>
>

Index bloat could be a factor too - performing a regular REINDEX on the 
relevant tables could be worth a try.

Regards

Mark


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance