Re: [PoC] Reducing planning time when tables have many partitions - Mailing list pgsql-hackers

From Thom Brown
Subject Re: [PoC] Reducing planning time when tables have many partitions
Date
Msg-id CAA-aLv7S4WZywzPPHQDgZ=4jgUDRfzNiRd0PScq883n-Xr+n4g@mail.gmail.com
Whole thread Raw
In response to Re: [PoC] Reducing planning time when tables have many partitions  (Thom Brown <thom@linux.com>)
Responses Re: [PoC] Reducing planning time when tables have many partitions
List pgsql-hackers
On Thu, 17 Nov 2022 at 11:20, Thom Brown <thom@linux.com> wrote:
>
> On Thu, 17 Nov 2022 at 09:31, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> >
> > On 2022-Nov-16, Thom Brown wrote:
> >
> > > Once the issue Tom identified has been resolved, I'd like to test
> > > drive newer patches.
> >
> > What issue?  If you mean the one from the thread "Reducing
> > duplicativeness of EquivalenceClass-derived clauses", that patch is
> > already applied (commit a5fc46414deb), and Yuya Watari's v8 series
> > applies fine to current master.
>
> Ah, I see..  I'll test the v8 patches.

No issues with applying.  Created 1024 partitions, each of which is
partitioned into 64 partitions.

I'm getting a generic planning time of 1415ms.  Is that considered
reasonable in this situation?  Bear in mind that the planning time
prior to this patch was 282311ms, so pretty much a 200x speedup.

Thom



pgsql-hackers by date:

Previous
From: Maxim Orlov
Date:
Subject: Re: [PoC] configurable out of disk space elog level
Next
From: Pavel Borisov
Date:
Subject: Re: Lockless queue of waiters in LWLock