Re: [PoC] Reducing planning time when tables have many partitions

amit <amitlangote09@gmail.com>

From: Amit Langote <amitlangote09@gmail.com>

To: David Rowley <dgrowleyml@gmail.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Yuya Watari <watari.yuya@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Dmitry Dolgov <9erthalion6@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>, jian he <jian.universality@gmail.com>, Alena Rybakina <lena.ribackina@yandex.ru>, Andrei Lepikhov <a.lepikhov@postgrespro.ru>, Thom Brown <thom@linux.com>, Zhang Mingli <zmlpostgres@gmail.com>

Date: 2025-04-10T06:28:55Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Update wording in optimizer/README for EquivalenceClasses
- d7c04db27aeb 18.0 landed
Speedup child EquivalenceMember lookup in planner
- d69d45a5a956 18.0 landed
Allow planner to use Merge Append to efficiently implement UNION
- 66c0185a3d14 17.0 cited
Remove trailing zero words from Bitmapsets
- a8c09daa8bb1 17.0 cited
Make Vars be outer-join-aware.
- 2489d76c4906 16.0 cited
Avoid making commutatively-duplicate clauses in EquivalenceClasses.
- a5fc46414deb 16.0 cited

On Thu, Apr 10, 2025 at 2:35 PM David Rowley <dgrowleyml@gmail.com> wrote:
> On Thu, 10 Apr 2025 at 16:57, Amit Langote <amitlangote09@gmail.com> wrote:
> >
> > On Thu, Apr 10, 2025 at 12:03 PM David Rowley <dgrowleyml@gmail.com> wrote:
> > > -Most operations on EquivalenceClasses should ignore child members.
> > > +Most operations on EquivalenceClasses needn't look at child members.
> > >
> > > Would that be ok?
> >
> > Yeah, I think that wording works well. It avoids sounding too strict
> > but still points things in the right direction.
>
> Thanks. Pushed.

Thank you.

-- 
Thanks, Amit Langote