Feedback-ID: ia2694551:Fastmail
Date: Wed, 22 Jan 2025 18:05:13 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Alexander Kuzmenkov <akuzmenkov@timescale.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Quadratic planning time for ordered paths over partitioned tables
Message-ID: <202501221705.slstsk3mmsv3@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALzhyqzvYqaZ9iaOQOpV2Ga=h4549UfaU6BFDNOpTU+scgnRUA@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202501221705.slstsk3mmsv3%40alvherre.pgsql>
Precedence: bulk

On 2025-Jan-22, Alexander Kuzmenkov wrote:

> On Wed, Jan 22, 2025 at 5:36 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> > I think this is closely related to the work Yuya Watari has been doing
> > at
> > https://postgr.es/m/CAJ2pMkZZHrhgQ5UV0y+STKqx7XVGzENMhL98UbKM-OArvK9dmA@mail.gmail.com
> > Perhaps you could contribute by reviewing that patch series.
> 
> Yeah, I'm referencing this one in my email, but it's a series of
> patches that does a major refactoring changing thousands of lines. I'm
> not sure when or if it's going to land, do you think applying a quick
> fix first would make sense? It makes trivial changes in one function.

I think it might go faster if you try it out and review it.

Which problems did you notice that make you think it's not committable?
Maybe you can propose solutions for those problems.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/