| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical replication without a Primary Key |
| Date: | 2017-12-07 18:49:37 |
| Message-ID: | CA+TgmoYGBSxW9w+4hfucPe7iRhJtpCRL=VwdFcjZw5zKkDj-vQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 7, 2017 at 9:43 AM, Petr Jelinek
<petr(dot)jelinek(at)2ndquadrant(dot)com> wrote:
> No it won't, it will update only one row, it does not try to find
> multiple matching rows.
Good, because that's exactly what it should do. I mean, if you have
on the master two tuples that are identical, and you update one of
them, then the replica had better update exactly one of them as well.
Since they are identical, it doesn't matter *which* one gets updated
on the replica, but if you update *both* of them on the replica, then
things are out of sync.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-12-07 18:52:21 | Re: Speeding up pg_upgrade |
| Previous Message | Robert Haas | 2017-12-07 18:45:29 | Re: pgsql: Support Parallel Append plan nodes. |