Re: Help tuning autovacuum - seeing lots of relationbloat
От | Jim C. Nasby |
---|---|
Тема | Re: Help tuning autovacuum - seeing lots of relationbloat |
Дата | |
Msg-id | 20060621193823.GI93655@pervasive.com обсуждение исходный текст |
Ответ на | Re: Help tuning autovacuum - seeing lots of relationbloat ("jody brownell" <jody.brownell@q1labs.com>) |
Ответы |
Re: Help tuning autovacuum - seeing lots of relationbloat
Re: Help tuning autovacuum - seeing lots of relationbloat Re: Help tuning autovacuum - seeing lots of relationbloat |
Список | pgsql-performance |
On Wed, Jun 21, 2006 at 01:21:05PM -0300, jody brownell wrote: > Jun 21 13:04:04 vanquish postgres[3311]: [19-1] DEBUG: "target": removed 5645231 row versions in 106508 pages > Jun 21 13:04:04 vanquish postgres[3311]: [19-2] DETAIL: CPU 3.37s/1.23u sec elapsed 40.63 sec. > Jun 21 13:04:04 vanquish postgres[3311]: [20-1] DEBUG: "target": found 5645231 removable, 1296817 nonremovable row versionsin 114701 pages > Jun 21 13:04:04 vanquish postgres[3311]: [20-2] DETAIL: 0 dead row versions cannot be removed yet. So the table contained 5.6M dead rows and 1.3M live rows. I think you should forget about having autovacuum keep this table in-check and add manual vacuum commands to your code. Autovac is intended to deal with 99% of use cases; this is pretty clearly in the 1% it can't handle. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
В списке pgsql-performance по дате отправления: