| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Duncan Sands <duncan(dot)sands(at)deepbluecap(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: range_agg extremely slow compared to naive implementation in obscure circumstances |
| Date: | 2023-02-01 14:51:11 |
| Message-ID: | 1367182.1675263071@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-02-01 15:32:52 | Re: BUG #17744: Fail Assert while recoverying from pg_basebackup |
| Previous Message | Tom Lane | 2023-02-01 14:42:43 | Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off |