Re: Avoiding vacuum full on an UPDATE-heavy table
| От | Vivek Khera |
|---|---|
| Тема | Re: Avoiding vacuum full on an UPDATE-heavy table |
| Дата | |
| Msg-id | x7n041msal.fsf@yertle.int.kciLink.com обсуждение исходный текст |
| Ответ на | Avoiding vacuum full on an UPDATE-heavy table (Bill Montgomery <billm@lulu.com>) |
| Список | pgsql-performance |
>>>>> "BM" == Bill Montgomery <billm@lulu.com> writes: BM> Is there any way to avoid doing a periodic VACUUM FULL on this table, BM> given the fairly radical usage pattern? Or is the (ugly) answer to BM> redesign our application to avoid this usage pattern? I'll bet upgrading to 7.4.2 clears up your problems. I'm not sure if it was in 7.3 or 7.4 where the index bloat problem was solved. Try to see if just reindexing will help your performance. Also, run a plain vacuum at least nightly so that your table size stays reasonable. It won't take much time on a table with only 50k rows in it. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
В списке pgsql-performance по дате отправления: