Re: Bad performance for a 3000 rows table updated permanently
От
Manfred Koizar
Тема
Re: Bad performance for a 3000 rows table updated permanently
Дата
Msg-id
rd3u8v0c0cogtrnlg7cc3k4hnhd57erc3m@4ax.com
Ответ на
Bad performance for a 3000 rows table updated permanently (fred-pg@jolliton.com)
Список
Дерево обсуждения
Bad performance for a 3000 rows table updated permanently fred-pg@jolliton.com
Re: Bad performance for a 3000 rows table updated permanently Manfred Koizar <mkoi-pg@aon.at>
Re: Bad performance for a 3000 rows table updated <fred-pg@jolliton.com>(Frederic Jolliton)
7.2 search/replace pl/pgsql Nabil Sayegh <postgresql@e-trolley.de>
Re: 7.2 search/replace pl/pgsql Josh Berkus <josh@agliodbs.com>
Re: 7.2 search/replace pl/pgsql Nabil Sayegh <postgresql@e-trolley.de>
Re: 7.2 search/replace pl/pgsql Josh Berkus <josh@agliodbs.com>
Re: 7.2 search/replace pl/pgsql "A.Bhuvaneswaran" <bhuvansql@myrealbox.com>
Re: Bad performance for a 3000 rows table updated Manfred Koizar <mkoi-pg@aon.at>
Re: Bad performance for a 3000 rows table updated fred-pg@jolliton.com (Frederic Jolliton)
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 по дате отправления
