On 07/12/17 21:19, Robert Haas wrote: > On Thu, Dec 7, 2017 at 2:53 PM, Chapman Flack <c...@anastigmatix.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
