I have a table like (pardon any errors, translating from internal names):
CREATE TABLE foo_bar (
foo_id STRING(1000),
bar_id STRING(1000),
PRIMARY KEY (foo_id, bar_id),
INDEX (bar_id)
);
In 2.1.5, this query would work:
INSERT INTO foo_bar (foo_id, bar_id) SELECT UNNEST('{"fooval1","fooval2","fooval2","fooval3"}'::STRING[]), 'barval1' ON CONFLICT (foo_id, bar_id) DO NOTHING;
But in 19.1.2, I get:
pq: duplicate key value (foo_id,bar_id)=('fooval2','barval1') violates unique constraint "primary"
Was that a result of this issue or something else? Is this backwards-incompatible change intended? Is this unique to this insert-from-select or select-unnest approach? The topic here (followup) was answered recently suggesting an UPSERT should work fine in these cases.
Any info is appreciated, thanks.