From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Gavin Roy <gavinr(at)aweber(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Regression in PL/PGSQL code using RETURN QUERY with Postgres 14 |
Date: | 2021-10-07 18:54:46 |
Message-ID: | af3b6087-881a-8a2e-8061-e96cee6cccc8@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/7/21 11:38 AM, Gavin Roy wrote:
> Hi All,
>
> My team was testing against Postgres 14 to ensure we could cleanly
> upgrade and we ran across a regression in our PL/PGSQL code related to
> the updates to RETURN QUERY.
>
> Our code which works in previous versions of Postgres uses UPDATE
> RETURNING and INSERT RETURNING in combination with RETURN QUERY. It
> appears that in the parallelism updates, RETURN QUERY now only accepts
> SELECT queries.
I'm pretty sure folks are going to want to see an example of the code
and the errors thrown in version 14.
>
> Was this an intentional change in behavior? We can easily refactor our
> PL/PGSQL functions to deal with the change, but if it was intentional,
> perhaps it should be documented.
>
> Regards,
>
> Gavin
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-10-07 19:05:00 | Re: Regression in PL/PGSQL code using RETURN QUERY with Postgres 14 |
Previous Message | Bruce Momjian | 2021-10-07 18:47:19 | Re: Currently running queries with actual arguments? |