Re: plpgsql: variables of domain of composite types are not correctly initialized

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql: variables of domain of composite types are not correctly initialized
Date: 2026-02-12 05:18:26
Message-ID: CAFj8pRBxsb2WqVwkRcTAn1YCEOw1jupWGq1HJKB-nvdgvUhRww@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

st 11. 2. 2026 v 22:10 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:

> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > I got a bug report for plpgsql_check related to domains of composite
> types.
> > While I played with code, maybe I found a bug:
>
> Indeed. Looks like exec_stmt_return's special case for a simple
> variable reference forgets to fill estate->rettype when the variable
> is a null record. This is an old bug, but I think we'd managed not
> to notice because that value isn't consulted unless we have to cast
> to a domain.
>
> The behavior we want is what exec_eval_datum does, and after looking
> at it for a minute I wondered why we don't just use exec_eval_datum
> instead of duplicating logic. The ROW case already does that, so
> we can fix the bug with strictly less code.
>
> regards, tom lane
>

Nice, Thank you

Pavel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Wong 2026-02-12 05:57:00 Re: PL/Julia: clarification on IN array parameters issue
Previous Message John Naylor 2026-02-12 04:58:37 Re: refactor architecture-specific popcount code