Re: BUG #16714: INSERT ON CONFLICT DO UPDATE fails to infer constraint if it's not at top-level partition

That's then either a docs bug. The documentation states:The constraint raised, it's specification equals and matches. It is ignored and raised exception is passed through. No, it's a bug;

Nevertheless, suppose I have a top-level partition bound primary key which covers all 4 columns and then my INSERT has all 4 of them in ON CONFLICT specification. This works as intended but: the exact index raised was not the one inferred since the top-level partition itself is not a default partition hence always empty hence it's index is always empty; an empty index cannot raise uniqueness violation exceptions then the one raised must be the leaf partition's (whichever it is). How could it not be a bug? Also: the certain partition to which data is to be inserted is computed at query planning stage the very stage where the planner could also find out if an index matching the given specification could be inferred since it's the only index that matters.

Also:That is exactly what this partitioning scheme is made for. Yet ridiculous constraint matching punishes for benefiting from partitioning.