From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Marc Millas <marc(dot)millas(at)mokadb(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: logical replication |
Date: | 2021-05-21 13:21:13 |
Message-ID: | d7f1bac2-8549-9d8e-956d-e635960ccaa4@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 5/21/21 8:41 AM, Marc Millas wrote:
> Hi,
>
> my POC in postgres 12.(important ?)
>
> if I setup 2 postgres clusters, and create a publication in one and a
> subscription in the other,
> and do on the pub an update which does not change the data (updating
> an existing record with same data) then this (useless) update go
> through replication.(ie consumes network ressource)
>
> what are ways to avoid this ?
> (I thought of a trigger to not execute the useless update, but I
> dont see how to do this)
> any ideas ?
>
> thanks
> PS: remarks about the meaning of this are off topic, thanks
>
>
Postgres provides exactly such a trigger. See
https://www.postgresql.org/docs/12/functions-trigger.html
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Millas | 2021-05-21 13:44:41 | Re: logical replication |
Previous Message | Marc Millas | 2021-05-21 12:41:31 | logical replication |