Re: var_is_nonnullable() fails to handle invalid NOT NULL constraints
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-15T00:51:03Z
Lists: pgsql-hackers
On Sun, Apr 12, 2026 at 6:33 PM SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com> wrote: > I tested this patch against the current HEAD (155c03ee) and it looks good. > Build & tests: Applies cleanly, compiles without warnings, all 247 regression tests > pass including the new subselect test case. Reproduced the bug before the patch > and verified it is fixed after the patch. Thanks for testing. > Looks like it needs to perform table_open/table_close multiple times depending upon > the number of output columns? I don't see it as a major concern but let others comment. I don't see it as a major concern either performance-wise. table_open here is just a hash lookup and refcount increment, and table_close is just a refcount decrement. And the call only happens in NOT IN cases, and only after sublink_testexpr_is_not_nullable has already returned true. So I've committed this patch. - Richard
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix var_is_nonnullable() to handle invalid NOT NULL constraints
- 363af93bdd24 19 (unreleased) landed