Re: Is a VACUUM or ANALYZE necessary after logical replication?

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Koen De Groote <kdg(dot)dev(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Is a VACUUM or ANALYZE necessary after logical replication?
Date: 2024-06-15 23:13:32
Message-ID: a6f211d1-a44c-4efe-8df2-d132f8f5e1f5@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 6/15/24 15:55, Koen De Groote wrote:
> I've gone over all of
> https://www.postgresql.org/docs/current/logical-replication.html
> <https://www.postgresql.org/docs/current/logical-replication.html> and
> the only mentions of the word "index" I could find was in relation to
> replica identity and examples of table definitions showing primary key
> indexes.
>
> Nothing is said about indexes. Maybe for good reason, maybe they are
> fully functionality immediately after replication?
>
> So the main question: Once a table is fully replicated, do I need to
> vacuum(analyze) that table, or are the indexes on that table already
> functional?

VACUUM/ANALYZE is not about making the index functional. The VACUUM
marks the space dead tuples occupy in the table and associated indexes
as available for recycling. The ANALYZE updates tables statistics to
help the planner make decisions on what query plan to use. On a fresh
table VACUUM will not be of much value, ANALYZE though will help by
creating up to date table statistics.

>
> Regards,
> Koen De Groote

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2024-06-16 04:53:31 Re: DROP COLLATION vs pg_collation question
Previous Message Koen De Groote 2024-06-15 22:55:50 Is a VACUUM or ANALYZE necessary after logical replication?