Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mX5CT-0007JN-Hi for pgsql-bugs@arkaria.postgresql.org; Sun, 03 Oct 2021 17:22:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mX5CR-00039Z-5W for pgsql-bugs@arkaria.postgresql.org; Sun, 03 Oct 2021 17:22:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mX5CQ-00039L-VC for pgsql-bugs@lists.postgresql.org; Sun, 03 Oct 2021 17:22:54 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mX5CO-0007NN-HU for pgsql-bugs@lists.postgresql.org; Sun, 03 Oct 2021 17:22:54 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 193HMmP93899524; Sun, 3 Oct 2021 13:22:49 -0400 From: Tom Lane To: Marc Bachmann cc: Robert Haas , jeremy@musicsmith.net, PostgreSQL mailing lists Subject: Re: BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan In-reply-to: <3735893.1633232886@sss.pgh.pa.us> References: <16040-eaacad11fecfb198@postgresql.org> <1741.1584847383@sss.pgh.pa.us> <1F2F75F0-27DF-406F-848D-8B50C7EEF06A@gmail.com> <3735893.1633232886@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Sat, 02 Oct 2021 23:48:06 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3899522.1633281768.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 03 Oct 2021 13:22:48 -0400 Message-ID: <3899523.1633281768@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > Marc Bachmann writes: >> A function that inserts data and tries to return with a table now resul= ts 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