On Tue, Aug 8, 2017 at 2:25 PM, Alexander Korotkov <aekorot...@gmail.com>
> Do we already assume that default btree opclass for array element type
> matches PK opclass when using @>> operator on UPDATE/DELETE of referenced
I believe so, since it's a polymorphic function.
> If so, we don't introduce additional restriction here...
You mean to remove the wrapper query ?
> GROUP BY would also use default btree/hash opclass for element type. It
> doesn't differ from DISTINCT from that point.
Then there's no going around this limitation,