Postgres Pro
Downloads
Home   >   mailing lists

Re: Is a VACUUM or ANALYZE necessary after logical replication? - Mailing list pgsql-general

From David G. Johnston
Subject Re: Is a VACUUM or ANALYZE necessary after logical replication?
Date
Msg-id CAKFQuwbkJ0z8Hz88u3xUtB55nMxzaycFxZAdB1t=BNUBn17YUg@mail.gmail.com
Whole thread Raw
In response to Is a VACUUM or ANALYZE necessary after logical replication?  (Koen De Groote <kdg.dev@gmail.com>)
List pgsql-general
Tree view
On Saturday, June 15, 2024, Koen De Groote <kdg.dev@gmail.com> wrote:
I've gone over all of 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?

The whole point of “logical” replication is that the inserts/updates/deletes are reapplied on the secondary against the table and the whatever triggers, indexes, or whatnot exist on that table in the secondary behave just as if you connected to the server directly and issued the corresponding SQL against it. As far as the replication system is concerned none of those things on the primary matter nor does it have to care about them on the secondary.

David J.

pgsql-general by date:

Previous
From: Achilleas Mantzios
Date:
Subject: Re: Is a VACUUM or ANALYZE necessary after logical replication?
Next
From: Karsten Hilbert
Date:
Subject: Re: DROP COLLATION vs pg_collation question