Re: range_agg extremely slow compared to naive implementation in obscure circumstances
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, Duncan Sands <duncan.sands@deepbluecap.com>, pgsql-bugs@lists.postgresql.org
Date: 2023-02-01T11:57:41Z
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).