Configuring AWS RDS for Postgres as source with a secondary readonly database

[MoeE]

Hi,

I read this community post (Link here) which indicates that if you are on PostgreSQL 16.x or later, and QR May 2024 or later, then you can do CDC from a secondary readonly database by enabling the read-write privilege on the user used to access the source DB. Previously this was not possible due to limitations in the endpoint which are in fact still present. Link here.

However, there were some limitations mentioned about DDL changes not being propagated from the main database to the secondary, and something about WAL heartbeats which was not explained. My question is, has anyone configured this before? and what are the limitations for configuring this?

Help with this is greatly appreciated. Thank you.

Regards,

Mohammed

[john_wang]

Hello Mohammed, @MoeE 

Thanks for opening the article.

Regarding the concerns:

>> there were some limitations mentioned about DDL changes not being propagated from the main database to the secondary

Yes, this is a limitation of PostgreSQL master/replica replication. The limitation exists in both 16.x , and 17.x (the current version). No way to overcome it in Qlik Replicate.

>> and something about WAL heartbeats which was not explained. 

I do not see any issue about enabling it. Anyway I did not try it yet. I'm planning to setup such an environment for a sanity test.

Regards,

John.