Re: Meaning of "constant" not honored when the variable is used as the actual for a proc's OUT formal paameter

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
Cc: pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Meaning of "constant" not honored when the variable is used as the actual for a proc's OUT formal paameter
Date: 2022-05-03 22:22:06
Message-ID: 2234967.1651616526@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bryn Llewellyn <bryn(at)yugabyte(dot)com> writes:
> The DO block runs without error and reports "INFO: 42". This is an unambiguous semantic error because "a" is declared "constant".

> Is this a known issue?

It is, see

https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=ccd10a9bf

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bryn Llewellyn 2022-05-03 22:48:27 Re: Meaning of "constant" not honored when the variable is used as the actual for a proc's OUT formal paameter
Previous Message Bryn Llewellyn 2022-05-03 22:03:32 Meaning of "constant" not honored when the variable is used as the actual for a proc's OUT formal paameter