Re: select count(*) performance (vacuum did not help)
| От | Gábor Farkas |
|---|---|
| Тема | Re: select count(*) performance (vacuum did not help) |
| Дата | |
| Msg-id | 46F7D207.3000901@nekomancer.net обсуждение исходный текст |
| Ответ на | Re: select count(*) performance (vacuum did not help) ("Heikki Linnakangas" <heikki@enterprisedb.com>) |
| Ответы |
Re: select count(*) performance (vacuum did not help)
|
| Список | pgsql-performance |
Heikki Linnakangas wrote: > Gábor Farkas wrote: >> - but in the past, the cron-job was not in place, so the table's size >> grew to around 800000 entries (in around 80 days) > > That bloated your table, so that there's still a lot of empty pages in > it. VACUUM FULL should bring it back to a reasonable size. Regular > normal non-FULL VACUUMs should keep it in shape after that. > hmm... can a full-vacuum be performed while the database is still "live" (i mean serving requests)? will the db still be able to respond to queries? or in a different way: if i do a full vacuum to that table only, will the database still serve data from the other tables at a normal speed? thanks, gabor
В списке pgsql-performance по дате отправления: