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

From: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
To: Tom Lane PostgreSQL <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:48:27
Message-ID: 7B50CB1F-0F02-4BA5-8E1B-22B3A52BAB8A@yugabyte.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
>
>> bryn(at)yugabyte(dot)com wrote:
>>
>> 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

Thanks for the instant response, Tom. It's uncanny that you spotted this on Saturday 30-Apr and I spotted it just three days later on Tuesday 3-May. One of us must be psychic.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Steve Baldwin 2022-05-04 03:50:29 Logical replication 'possible' problem
Previous Message Tom Lane 2022-05-03 22:22:06 Re: Meaning of "constant" not honored when the variable is used as the actual for a proc's OUT formal paameter