| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Multi-Master Logical Replication |
| Date: | 2022-04-28 06:48:36 |
| Message-ID: | f8b14ba838c4948365747cd8d3c220152e5bf959.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2022-04-28 at 09:49 +1000, Peter Smith wrote:
> To prevent the circular recursive problem Vignesh is developing a
> patch [1] that introduces new SUBSCRIPTION options "local_only" (for
> publishing only data originating at the publisher node) and
> "copy_data=force". Using this patch, we have created a script [2]
> demonstrating how to set up all the above multi-node examples. An
> overview of the necessary steps is given in the next section.
I am missing a discussion how replication conflicts are handled to
prevent replication from breaking or the databases from drifting apart.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-04-28 06:49:42 | Re: Possible corruption by CreateRestartPoint at promotion |
| Previous Message | Yugo NAGATA | 2022-04-28 06:40:11 | Re: Implementing Incremental View Maintenance |