Re: BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan

From: Marc Bachmann <marc(dot)brookman(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, jeremy(at)musicsmith(dot)net, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan
Date: 2021-10-03 18:01:56
Message-ID: F67D5BE1-3FCA-4106-AC75-0AEF6DD9F8A2@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

I’m happy to help.
And sorry that you had to go through that many changes right after the release.

Kind regards
Marc

> On 3 Oct 2021, at 19:22, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I wrote:
>> Marc Bachmann <marc(dot)brookman(at)gmail(dot)com> writes:
>>> A function that inserts data and tries to return with a table now results in the error `query is not a SELECT`.
>>> In previous versions that query succeeded.
>
>> Hmm ... I'm a bit surprised that that worked before, but since it did,
>> we shouldn't break it.
>
> Fix pushed, thanks for the report!
>
> regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Dilger 2021-10-03 22:20:20 Re: BUG #17212: pg_amcheck fails on checking temporary relations
Previous Message Tom Lane 2021-10-03 17:22:48 Re: BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-10-03 19:14:58 Triage on old commitfest entries
Previous Message vignesh C 2021-10-03 17:55:27 Re: Added schema level support for publication.