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

From Tom Lane
Subject Re: Re: Unexpected result from ALTER FUNCTION— looks like a bug
Date
Msg-id 2658371.1650422377@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unexpected result from ALTER FUNCTION— looks like a bug  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Tue, Apr 19, 2022 at 7:07 PM Bryn Llewellyn <bryn@yugabyte.com>
> wrote:
>> This is the bug.

> While I haven't experimented with this for confirmation, what you are
> proposing here (set + parallel safe) is an impossible runtime
> combination (semantic rule) but perfectly valid to write syntactically.

I'm not sure that that's actually disallowed.  In any case, Bryn's
right, the combination of a SET clause and a PARALLEL clause is
implemented incorrectly in AlterFunction.  Careless coding :-(

            regards, tom lane



pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Unexpected result from ALTER FUNCTION— looks like a bug
Next
From: Julien Rouhaud
Date:
Subject: Re: Unexpected result from ALTER FUNCTION— looks like a bug