Index tuple deduplication limitations in pg13

2020-08-17 Thread Matthias van de Meent
Hi, I was reading through the new features of PG13 (beta), and noticed that deduplication is disabled for float(4, 8) and numeric (and jsonb, ...) due to that the datums of those types could be not binary equal, but equal according for the opclass used. But, if the ordering of operator-class equa

Re: Index tuple deduplication limitations in pg13

2020-08-18 Thread Matthias van de Meent
On Tue, 18 Aug 2020 at 18:44, Peter Geoghegan wrote: > > On Mon, Aug 17, 2020 at 11:44 PM Matthias van de Meent > wrote: > > But, if the ordering of operator-class equal tuples is already > > system-defined, could the physical ordering of index tuples in a btree > >

Re: Index tuple deduplication limitations in pg13

2020-08-18 Thread Matthias van de Meent
On Tue, 18 Aug 2020 at 22:00, Peter Geoghegan wrote: > > On Tue, Aug 18, 2020 at 11:52 AM Matthias van de Meent > wrote: > > Given that the above could work, the current btree tuple ordering is > > not optimized for opclass-equal but datum image-distinct values: > >