Re: PG13 Autovacuum for Insert
От | Keith Fiske |
---|---|
Тема | Re: PG13 Autovacuum for Insert |
Дата | |
Msg-id | CAODZiv5M+g7DmtVYi2VqXWh44FNgnBNMkwEFbC_WCLLDKn+=7g@mail.gmail.com обсуждение исходный текст |
Ответ на | PG13 Autovacuum for Insert (Raj kumar <rajkumar820999@gmail.com>) |
Ответы |
Re: PG13 Autovacuum for Insert
|
Список | pgsql-admin |
On Thu, Jul 8, 2021 at 8:27 AM Raj kumar <rajkumar820999@gmail.com> wrote:
Hi all,In PG13, we have a new feature where autovacuum gets triggered based on Insert threshold. I wanted to know why we need autovacuum for Insert workloads, as there won't be any dead tuples because of them and we already have Auto analyze for inserts till PG12.Thanks,Raj Kumar Narendiran
Vacuum also keeps the freespacemap and visibility maps updated as well. Not quite as critical for insert-only tables, but it can still influence query planning. Having an up to date visibility-map can help index-only scans happen more frequently if possible.
--
This section of the documentation is a really good read for understanding vacuuming and MVCC in PostgreSQL.
В списке pgsql-admin по дате отправления: