Re: Wrong unsafe-flag test in check_output_expressions() - Mailing list pgsql-hackers

From David Rowley
Subject Re: Wrong unsafe-flag test in check_output_expressions()
Date
Msg-id CAApHDvpb8nHDXF+ZS4BG=k=-4ykVpP6EYtsV7=rjNezun8CrQg@mail.gmail.com
Whole thread
In response to Wrong unsafe-flag test in check_output_expressions()  (Richard Guo <guofenglinux@gmail.com>)
Responses Re: Wrong unsafe-flag test in check_output_expressions()
List pgsql-hackers
On Mon, 1 Jun 2026 at 20:27, Richard Guo <guofenglinux@gmail.com> wrote:
>
> I happened to notice $subject when working on a bug-fix near-by.
>
>    /* If subquery uses window functions, check point 4 */
>    if (subquery->hasWindowFuncs &&
>        (safetyInfo->unsafeFlags[tle->resno] &
>         UNSAFE_NOTIN_DISTINCTON_CLAUSE) == 0 &&
>        !targetIsInAllPartitionLists(tle, subquery))
>    {
>        /* not present in all PARTITION BY clauses, so mark it unsafe */
>        safetyInfo->unsafeFlags[tle->resno] |= UNSAFE_NOTIN_PARTITIONBY_CLAUSE;
>        continue;
>    }

Yes, that's not intentional. Your proposed fix looks correct. Are you
happy to go ahead with pushing and backpatching that?

Wondering, did you spot that with eyes or tool assist?

David



pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: Fix bug of CHECK constraint enforceability recursion
Next
From: Sami Imseih
Date:
Subject: Re: Vacuumlo improvements