Re: Row pattern recognition

From: Henson Choi <assam258(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: zsolt(dot)parragi(at)percona(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, peter(at)eisentraut(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Row pattern recognition
Date: 2026-03-12 00:39:57
Message-ID: CAAAe_zDAQWje=SK65hstqEwMgbQGRH4P1=5yOmvgT7m2Mz8Qbw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2026년 3월 12일 (목) AM 9:21, Tatsuo Ishii <ishii(at)postgresql(dot)org>님이 작성:

> Hi Zsolt,
>
> Thanks for the report and the test case!
>
> > Good catch, Zsolt. You're right ― the return value of
> > coerce_to_boolean() must be assigned back to te->expr, otherwise
> > any implicit cast (e.g., a user-defined type with an assignment
> > cast to boolean) is silently discarded.
> >
> > The fix is straightforward:
> >
> > foreach_ptr(TargetEntry, te, defineClause)
> > te->expr = (Expr *) coerce_to_boolean(pstate, (Node *) te->expr,
> > "DEFINE");
> >
> > I've confirmed that your example query produces incorrect results
> > without the fix (the truthyint value is evaluated as-is without
> > the cast) and correct results with it.
> >
> > Patch 13 is attached with the fix and a regression test case based
> > on your example.
>
> Yeah, current patch needs to be fixed. Question is, the output of the
> expression of DEFINE clause must be a strict boolean or, it is allowed
> to accept an expression coercive to boolean?
>
> If we prefer the former, we should use exprType() instead.
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS K.K.
> English: http://www.sraoss.co.jp/index_en/
> Japanese:http://www.sraoss.co.jp
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Henson Choi 2026-03-12 00:44:29 Re: Row pattern recognition
Previous Message Tatsuo Ishii 2026-03-12 00:21:25 Re: Row pattern recognition