Re: Partition pruning can incorrectly exclude a RANGE default partition

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tender Wang <tndrwang(at)gmail(dot)com>
Cc: Chengpeng Yan <chengpeng_yan(at)outlook(dot)com>, Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Partition pruning can incorrectly exclude a RANGE default partition
Date: 2026-07-31 03:40:59
Message-ID: CAApHDvqM2C303FPu65x7sWhnCEyUVKqH1OrTOn-n7baowoHz=A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 30 Jul 2026 at 17:29, Tender Wang <tndrwang(at)gmail(dot)com> wrote:
> David Rowley <dgrowleyml(at)gmail(dot)com> 于2026年7月30日周四 11:47写道：
> > In other words, I think #2 is the correct fix. The attached v1-0001
> > patchifies that method.
> >
> Yes, I agree that #2 is the better approach. It is simpler, more
> straightforward, and has less impact on the existing code.

I made some test adjustments and pushed.

Thanks for the report, Jacob.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-07-31 03:48:06 Re: Fix optind handling inconsistency in getopt_long() for missing argument
Previous Message Xuneng Zhou 2026-07-31 03:39:11 Re: Implement waiting for wal lsn replay: reloaded