Re: range_agg extremely slow compared to naive implementation in obscure circumstances - Mailing list pgsql-bugs

From Tom Lane
Subject Re: range_agg extremely slow compared to naive implementation in obscure circumstances
Date
Msg-id 1367182.1675263071@sss.pgh.pa.us
Whole thread Raw
In response to Re: range_agg extremely slow compared to naive implementation in obscure circumstances  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-bugs
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2023-Jan-31, David Rowley wrote:
>> It might be better if we had multirange_canonicalize() deserialize
>> these once and used some representation that could more easily be
>> qsorted. I'm not planning on doing any work on it though.

> Yeah, maybe it would be possible to have an in-memory representation
> that doesn't require any deparsing, and keep the compact representation
> to be used only for in-data-page storage.  How to do this within the
> constraints of the Datum abstraction is not clear to me.

Perhaps the "expanded datum" mechanism would serve?

src/include/utils/expandeddatum.h

It might be too heavyweight for this application, but I'm not sure.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
Next
From: Andres Freund
Date:
Subject: Re: BUG #17744: Fail Assert while recoverying from pg_basebackup