Impact of replication when executing “Vacuum” in PostgreSQL-based source

[iti-attunity-sup]

We plan to run “Vacuum” on PostgreSQL-based source.
We expect that a large amount of Wal logs will be output during this process.
However, since these Wal logs do not represent table change operations,
we understand that Qlik Replicate will read the Wal logs but will not replicate them to the target.
Is this understanding correct?

If the above understanding is correct, it may take some time to load the wall, but is there anything else that could affect replication?

Best Reguards

Hironori

[DesmondWOO · Accepted solution]

Hi Hironori san, @iti-attunity-sup,

Thank you for reaching out to the Qlik Community.

I conducted a test by running VACUUM FULL public.MyTable and then checked the replication slot. I only found two changes: BEGIN and COMMIT.

Since Qlik Replicate reads changes from the replication slot, I suggest running VACUUM in the test environment and then checking the replication slot to see what changes are generated by the VACUUM command.

Regards,
Desmond