On Thu, Aug 25, 2016 at 11:49 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > I think the point is that given the way he's set up the test case, > there should be no duplicate violation in the plain unique index > unless there is one in the arbiter index. So assuming that INSERT > tests the arbiter indexes first, there shouldn't be an error. > Maybe it doesn't do that, but it seems like it would be a good idea > if it did.
Oh, yeah. This is arguably an example of inference failing to infer multiple unique indexes as arbiters. Inference could, in principle, recognize that the second unique index is equivalent to the first, but doesn't. (I don't think that it matters which order anything is tested in, though, because not finding a dup value in the arbiter index does not guarantee that there won't be one in the other index. There is no locking when no conflict is initially found, and so no guarantees here.) Anyway, I don't have a lot of sympathy for this point of view, because the scenario is completely contrived. You have to draw the line somewhere. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers