| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, Ronald Cruz <cruz(at)rentec(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Ford <pford(at)rentec(dot)com>, "Aaron J(dot) Garcia" <agarcia(at)rentec(dot)com> |
| Subject: | Re: Query result differences between PostgreSQL 17 vs 16 |
| Date: | 2025-03-11 22:03:40 |
| Message-ID: | Z9CzPA0W3Zyvqb6g@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Mar 4, 2025 at 04:30:26PM +0900, Richard Guo wrote:
> On Tue, Mar 4, 2025 at 12:22 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> > > Here is an updated patch, which also includes the test case you found
> > > proving the no-clone-quals limitation in restriction_is_always_false
> > > is also needed.
>
> > LGTM.
>
> Pushed and back-patched to v17. The fix will be included in next
> minor release (17.5).
Uh, if we fixed this for NULL optimization and backpatched, should we do
the same for:
Parameter NOT NULL to CREATE DOMAIN not the same as CHECK (VALUE IS NOT NULL)
https://www.postgresql.org/message-id/flat/173591158454.714.7664064332419606037%40wrigleys.postgresql.org
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-11 22:19:49 | Re: Query result differences between PostgreSQL 17 vs 16 |
| Previous Message | Peter Wright | 2025-03-11 21:54:03 | Re: Unqualified name not resolved in function called from materialized view (17.4) |