public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: Koen De Groote <[email protected]>
Cc: PostgreSQL General <[email protected]>
Subject: Re: Is a VACUUM or ANALYZE necessary after logical replication?
Date: Sun, 16 Jun 2024 00:09:17 -0700
Message-ID: <CAKFQuwbkJ0z8Hz88u3xUtB55nMxzaycFxZAdB1t=BNUBn17YUg@mail.gmail.com> (raw)
In-Reply-To: <CAGbX52EwdrpPLyRuRRpnbhUqfQYijVz3cShSMuoXrs2Lgkod5Q@mail.gmail.com>
References: <CAGbX52EwdrpPLyRuRRpnbhUqfQYijVz3cShSMuoXrs2Lgkod5Q@mail.gmail.com>
On Saturday, June 15, 2024, Koen De Groote <[email protected]> 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.
view thread (4+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Is a VACUUM or ANALYZE necessary after logical replication?
In-Reply-To: <CAKFQuwbkJ0z8Hz88u3xUtB55nMxzaycFxZAdB1t=BNUBn17YUg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox