Re: BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan
Date
Msg-id 3735893.1633232886@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Marc Bachmann <marc.brookman@gmail.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.  It looks like this was an accidental side-effect
of refactoring rather than something intentional.  Will look closer
tomorrow or so.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Marc Bachmann
Date:
Subject: Re: BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan
Next
From: Mark Dilger
Date:
Subject: Re: BUG #17212: pg_amcheck fails on checking temporary relations