Re: BUG #2784: Performance serious degrades over a period of a month
От | Heikki Linnakangas |
---|---|
Тема | Re: BUG #2784: Performance serious degrades over a period of a month |
Дата | |
Msg-id | 456C189F.7080103@enterprisedb.com обсуждение исходный текст |
Ответ на | BUG #2784: Performance serious degrades over a period of a month ("Michael Simms" <michael@tuxgames.com>) |
Список | pgsql-bugs |
Michael Simms wrote: > The following bug has been logged online: > > Bug reference: 2784 > Logged by: Michael Simms > Email address: michael@tuxgames.com > PostgreSQL version: 8.1.4 > Operating system: Linux kernel 2.6.12 > Description: Performance serious degrades over a period of a month > Details: > > OK, we have a database that runs perfectly well after a dump and restore, > but over a period of a month or two, it just degrades to the point of > uselessness. > vacuumdb -a is run every 24 hours. We have also run for months at a time > using -a -z but the effect doesnt change. You might have a hung transaction that never finishes open, which prevents vacuum from removing old tuple versions. Or you might have too low FSM settings as others suggested. I'd try running VACUUM VERBOSE by hand, and taking a good look at the output. If there's nothing obviously wrong with it, please send the output back to the list (or pgsql-performance, as Tom suggested), and maybe we can help. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
В списке pgsql-bugs по дате отправления: