Re: Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable
Date
Msg-id 3153441.1644949077@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable  ("Delaney, Ed" <Ed.Delaney@ellucian.com>)
List pgsql-bugs
"Delaney, Ed" <Ed.Delaney@ellucian.com> writes:
> I could not find a reference to this change in the release notes, but since it is a breaking change, perhaps it
shouldbe noted? 

The 2021-11-11 release notes all say

  * Don't discard a cast to the same type with unspecified type modifier (Tom Lane)

    For example, if column f1 is of type numeric(18,3), the parser used to
    simply discard a cast like f1::numeric, on the grounds that it would
    have no run-time effect. That's true, but the exposed type of the
    expression should still be considered to be plain numeric, not
    numeric(18,3). This is important for correctly resolving the type of
    larger constructs, such as recursive UNIONs.

            regards, tom lane



pgsql-bugs by date:

Previous
From: "Delaney, Ed"
Date:
Subject: Re: Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade