Re: Unexpected result from ALTER FUNCTION— looks like a bug
| От | David G. Johnston |
|---|---|
| Тема | Re: Unexpected result from ALTER FUNCTION— looks like a bug |
| Дата | |
| Msg-id | CAKFQuwaYCFPt_vYaX-buP8enb7yfhJRBsa5f+YWHCPkZEcbRHw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Unexpected result from ALTER FUNCTION— looks like a bug (Bryn Llewellyn <bryn@yugabyte.com>) |
| Ответы |
Re: Unexpected result from ALTER FUNCTION— looks like a bug
|
| Список | 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 по дате отправления: