Re: Bad performance for a 3000 rows table updated permanently

From: Manfred Koizar <mkoi-pg(at)aon(dot)at>
To: fred-pg(at)jolliton(dot)com
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Bad performance for a 3000 rows table updated permanently
Date: 2003-04-05 17:27:48
Message-ID: rd3u8v0c0cogtrnlg7cc3k4hnhd57erc3m@4ax.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Sat, 05 Apr 2003 16:39:42 +0200, fred-pg(at)jolliton(dot)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

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2003-04-05 18:10:47 Re: [NOVICE] Timestamp with time zone change (error) in 7.3.2?
Previous Message Kevin Coyner 2003-04-05 16:40:49 Re: configuring postgresql on the browser