Re: Posrgres speed problem - solved?

Поиск
Список
Период
Сортировка
Искать
От
Guido Neitzer
Тема
Re: Posrgres speed problem - solved?
Дата
Msg-id
F4703D84-5BA7-44D6-B6F9-78C5D89CE76C@pharmaline.de
Ответ на
Список
Дерево обсуждения
Posrgres speed problem Ruben Rubio Rey <ruben@rentalia.com>
Re: Posrgres speed problem "Dave Dutcher" <dave@tridecap.com>
Re: Posrgres speed problem Michael Fuhr <mike@fuhr.org>
Re: Posrgres speed problem "Jim C. Nasby" <jnasby@pervasive.com>
Re: Posrgres speed problem Ruben Rubio Rey <ruben@rentalia.com>
Re: Posrgres speed problem Sven Geisler <sgeisler@aeccom.com>
Re: Posrgres speed problem - solved? Ruben Rubio Rey <ruben@rentalia.com>
Re: Posrgres speed problem - solved? Guido Neitzer <guido.neitzer@pharmaline.de>
Re: Posrgres speed problem - solved? Ruben Rubio Rey <ruben@rentalia.com>
Re: Posrgres speed problem - solved! Ruben Rubio Rey <ruben@rentalia.com>
Re: Posrgres speed problem - solved! Guido Neitzer <guido.neitzer@pharmaline.de>
On 13.06.2006, at 8:44 Uhr, Ruben Rubio Rey wrote:

> Tonight database has been vacumm full and reindex (all nights  
> database do it)
>
> Now its working fine. Speed is as spected. I ll be watching that  
> sql ...
> Maybe the problem exists when database is busy, or maybe its  
> solved ...

Depending on the usage pattern the nightly re-index / vacuum analyse  
is suboptimal. If you have high insert/update traffic your  
performance will decrease over the day and will only be good in the  
morning hours and I hope this is not what you intend to have.

Autovacuum is the way to go, if you have "changing content". Perhaps  
combined with vacuum analyse in a nightly or weekly schedule. We do  
this weekly.

cug
В списке pgsql-performance по дате отправления
От: J. Andrew Rogers
Дата:
От: Ruben Rubio Rey
Дата:
FAQ