From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Logical replication without a Primary Key |
Date: | 2017-12-08 02:29:22 |
Message-ID: | 3992d39f-b294-85e1-6b40-92f0848e5895@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/12/17 21:19, Robert Haas wrote:
> On Thu, Dec 7, 2017 at 2:53 PM, Chapman Flack <chap(at)anastigmatix(dot)net> wrote:
>> On 12/07/2017 02:38 PM, Joshua D. Drake wrote:
>>> A B C
>>> foo,bar,baz
>>> foo,bar,baz
>>>
>>> And then I say:
>>>
>>> UPDATE test set A = 1 where C = baz
>>>
>>> I have updated two rows because there is no primary key to identify the
>>> differences. Both of those rows should be updated and thus replicated
>>
>> Would the subscriber see two records reporting update of a
>> foo,bar,baz row to 1, so it would do that to (arbitrarily)
>> one of them the first time, and (necessarily) the other, the
>> second time?
>
> Exactly.
>
> (I think.)
>
Yes, that how it was designed to work.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2017-12-08 02:36:33 | Re: Usage of epoch in txid_current |
Previous Message | Peter Geoghegan | 2017-12-08 02:23:28 | Re: PostgreSQL crashes with SIGSEGV |