Hello All,
I have a question regarding decoding of WALs in case of pglogical is used.
From my research, in native logical replication, decoding of WALs happens for all changes of the database irrespective of tables in replication. However, if pglogical is used, decoding happens ONLY for the tables which are in replication? Or Slot streams all the changes and pglogical_output plugin filters the changes based on replication sets?
I was going through pglogical_output internal document, and under "Architecture and high level interaction" section - "PostgreSQL then calls functions in this plugin to send it a stream of transactions to decode and translate into network messages.". So, it decodes transactions related to the tables in replication set? Or am I misunderstanding it?
--
Blog: bajis-postgres.blogspot.in/
I have a question regarding decoding of WALs in case of pglogical is used.
From my research, in native logical replication, decoding of WALs happens for all changes of the database irrespective of tables in replication. However, if pglogical is used, decoding happens ONLY for the tables which are in replication? Or Slot streams all the changes and pglogical_output plugin filters the changes based on replication sets?
I was going through pglogical_output internal document, and under "Architecture and high level interaction" section - "PostgreSQL then calls functions in this plugin to send it a stream of transactions to decode and translate into network messages.". So, it decodes transactions related to the tables in replication set? Or am I misunderstanding it?
--
Regards,
Baji Shaik,
Senior Database Consultant | OpenSCG