From: | konstantin knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Subject: | Selective logical replication |
Date: | 2015-11-19 08:48:20 |
Message-ID: | 81E39AF3-FF55-4F65-88D6-05D14E35EBE5@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I want to use logical replication for implementing multimaster (so all nodes are both sending and receiving changes).
But there is one "stupid" problem: how to prevent infinite recursion and not to rereplicate replicated data.
I.e. node receives change set from some other node, applies it within some transaction, it is written to the log and ... is replicated to other nodes.
In my experiments with receiver_raw/decoder_raw infinite recursion actually doesn't happen because unique constraint violation.
But it is neither nice, neither efficient way of stopping infinite recursion.
I wonder if there is some better way to prevent some particular transaction from been replicated?
Thanks in advance,
Konstantin
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2015-11-19 08:53:26 | Re: [DESIGN] ParallelAppend |
Previous Message | Erik Rijkers | 2015-11-19 08:41:42 | Re: warning: HS_KEY redefined (9.5 beta2) |