| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | 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 11:57:41 |
| Message-ID: | 20230201115741.qfcjbm4jyji4etvn@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"El sabio habla porque tiene algo que decir;
el tonto, porque tiene que decir algo" (Platon).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-01 14:42:43 | Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off |
| Previous Message | hubert depesz lubaczewski | 2023-02-01 11:10:57 | Re: BUG #17766: Issue in asc, limit and offset for pagination. |