Re: Unexpected result from ALTER FUNCTION— looks like a bug - Mailing list pgsql-general

From David G. Johnston
Subject Re: Unexpected result from ALTER FUNCTION— looks like a bug
Date
Msg-id CAKFQuwaYCFPt_vYaX-buP8enb7yfhJRBsa5f+YWHCPkZEcbRHw@mail.gmail.com
Whole thread Raw
In response to Re: Unexpected result from ALTER FUNCTION— looks like a bug  (Bryn Llewellyn <bryn@yugabyte.com>)
Responses Re: Unexpected result from ALTER FUNCTION— looks like a bug  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On Wed, Apr 20, 2022 at 10:45 AM Bryn Llewellyn <bryn@yugabyte.com> wrote:
> tgl@sss.pgh.pa.us wrote:
>

> In any case, Bryn's right, the combination of a SET clause and a PARALLEL clause is implemented incorrectly in AlterFunction.

I'm taking what I've read in the responses to mean that the testcase I showed is considered to be evidence of a bug (i.e. there are no semantic restrictions) and that fix(es) are under consideration.

The test case was good.  I made an uninformed assumption that proved to be untrue.

The patch was written and applied yesterday, at Tom's "Yeah, I arrived at the same fix." email.


(I haven't figured out what the official way to reference a commit is, I use the GitHub clone for research so there ya go).

David J.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 10.20 crashes / Antivirus
Next
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 10.20 crashes / Antivirus