Re: PG13 Autovacuum for Insert

From: Raj kumar <rajkumar820999(at)gmail(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: PG13 Autovacuum for Insert
Date: 2021-07-08 15:08:48
Message-ID: CACxU--UnWduV2aU7nB8nrUTPtt0X=jQGAWeXbM6D9PswjhWEyA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thanks Keith and Ron. Now, I understood better.

Thanks,
Raj Kumar Narendiran.

On Thu, 8 Jul 2021, 20:29 Ron, <ronljohnsonjr(at)gmail(dot)com> wrote:

> On 7/8/21 8:38 AM, Keith Fiske wrote:
> [snip]
> > 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.
>
> We've got INSERT-only tables, and the query planner only used sequential
> scans (on a freshly loaded 6TB database) until I vacuumed all tables,
>
> --
> Angular momentum makes the world go 'round.
>
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ivan Petrov 2021-07-08 18:37:44 Bad value for type BigDecimal : Infinity
Previous Message Ron 2021-07-08 14:59:36 Re: PG13 Autovacuum for Insert