Re: Bad performance for a 3000 rows table updated permanently - Mailing list pgsql-novice

From Manfred Koizar
Subject Re: Bad performance for a 3000 rows table updated permanently
Date
Msg-id rd3u8v0c0cogtrnlg7cc3k4hnhd57erc3m@4ax.com
Whole thread Raw
In response to Bad performance for a 3000 rows table updated permanently  (fred-pg@jolliton.com)
Responses Re: Bad performance for a 3000 rows table updated  (<fred-pg@jolliton.com>(Frederic Jolliton))
List pgsql-novice
On Sat, 05 Apr 2003 16:39:42 +0200, fred-pg@jolliton.com wrote:
>I have a table with 3000 rows (this number is almost constant, and
>never decrease)

>A stored procedure (PL/pgSQL) is called with an average of 14 times
>per seconds and, 99% of the time, this result on one SELECT followed
>by an UPDATE on table "data".

So there are almost 900 updates per minute.

Do a VACUUM FULL once and then a VACUUM every minute.  From time to
time do ANALYSE or VACUUM ANALYSE.  MAX_FSM_RELATIONS should be no
problem, but make sure that MAX_FSM_PAGES is not too low.

Servus
 Manfred


pgsql-novice by date:

Previous
From: Kevin Coyner
Date:
Subject: Re: configuring postgresql on the browser
Next
From: Don Patou
Date:
Subject: Re: configuring postgresql on the browser