Re: postgres bogged down beyond tolerance
| От | Kevin Grittner |
|---|---|
| Тема | Re: postgres bogged down beyond tolerance |
| Дата | |
| Msg-id | 473B1535.EE98.0025.0@wicourts.gov обсуждение |
| Ответ на | Re: postgres bogged down beyond tolerance ("Scott Marlowe" <scott.marlowe@gmail.com>) |
| Ответы |
Re: postgres bogged down beyond tolerance
|
| Список | pgsql-admin |
>>> On Wed, Nov 14, 2007 at 3:16 PM, in message <dcc563d10711141316u53338170l5d31d7723c8dc30b@mail.gmail.com>, "Scott Marlowe" <scott.marlowe@gmail.com> wrote: > On Nov 14, 2007 2:26 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote: >> INFO: vacuuming "public.allele" >> INFO: "allele": found 2518282 removable, 1257262 nonremovable row versions >> in 31511 pages >> Total free space (including removable row versions) is 161940948 bytes. > It looks to me like your tables were bloated. After running vacuum > full your cron should run faster now. Isn't it usually a good idea to REINDEX after using VACUUM FULL to recover from this level of bloat? -Kevin
В списке pgsql-admin по дате отправления: