Re: Index space growing even after cleanup via autovacuum in Postgres 9.2
От | Francisco Olarte |
---|---|
Тема | Re: Index space growing even after cleanup via autovacuum in Postgres 9.2 |
Дата | |
Msg-id | CA+bJJbx3hfPQFZEWQ-Yzw-vQ2NBCuffW231ATp+cjb+OD6nzyA@mail.gmail.com обсуждение исходный текст |
Ответ на | Index space growing even after cleanup via autovacuum in Postgres 9.2 (Tirthankar Barari <tbarari@verizon.com>) |
Ответы |
Re: Index space growing even after cleanup via autovacuum
in Postgres 9.2
Re: Index space growing even after cleanup via autovacuum in Postgres 9.2 |
Список | pgsql-general |
Hi: On Thu, Jan 9, 2014 at 7:50 PM, Tirthankar Barari <tbarari@verizon.com> wrote: > We have a table where we insert about 10 million rows everyday. We keep 14 > day's worth of entries (i.e. 140 mil). A scheduled task wakes up every day > and deletes all entries past the 14 day window (i.e. deletes entries from > the 15th day in the past). Not related to your vacuum problem, but if your pattern is something like deleting everything inserted 15 days ago you may want to think of using partitioning or simple inheritance. Make the scheduled task create a new partition/child table, redirect insertions to it, drop the oldest partition. Also, if the pattern is insert-only all the time, delete whole day, it may be easier to exclude the table from autovacuum and make the scheduled task vacuum the table after deleting. Francisco Olarte.
В списке pgsql-general по дате отправления: