From: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: logical replication |
Date: | 2021-05-21 13:44:41 |
Message-ID: | CADX_1abWs-xy1TM0ixQf-yJ=LfOrzTpDFxTqo8wpU0f7vDrEnw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
perfect :-)
thanks
Marc MILLAS
Senior Architect
+33607850334
www.mokadb.com
On Fri, May 21, 2021 at 3:21 PM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> 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 | Nagaraj Raj | 2021-05-21 16:38:30 | Re: Partition with check constraint with "like" |
Previous Message | Andrew Dunstan | 2021-05-21 13:21:13 | Re: logical replication |