Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1di0gS-00010u-C5 for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Aug 2017 15:56:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1di0gR-0008Jq-Ro for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Aug 2017 15:56:39 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1di0gR-0008Jg-43 for pgsql-hackers@postgresql.org; Wed, 16 Aug 2017 15:56:39 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1di0gO-0004VZ-43 for pgsql-hackers@postgresql.org; Wed, 16 Aug 2017 15:56:37 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v7GFuYq1026169; Wed, 16 Aug 2017 11:56:34 -0400 From: Tom Lane To: Robert Haas cc: "pgsql-hackers@postgresql.org" Subject: Re: [COMMITTERS] pgsql: Simplify plpgsql's check for simple expressions. In-reply-to: References: <23425.1502822098@sss.pgh.pa.us> <31094.1502827694@sss.pgh.pa.us> <29231.1502831727@sss.pgh.pa.us> <7013.1502836842@sss.pgh.pa.us> <23848.1502895834@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Wed, 16 Aug 2017 11:22:29 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <26167.1502898994.1@sss.pgh.pa.us> Date: Wed, 16 Aug 2017 11:56:34 -0400 Message-ID: <26168.1502898994@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Robert Haas writes: > On Wed, Aug 16, 2017 at 11:03 AM, Tom Lane wrote: >> Well, it has subplans, so formally I think it's restricted not unsafe >> --- but the parallel_safe marking on constructed paths/plans is only >> safe/not-safe, not a three-way. > True, but when parallel_safe it not set, that means it's not > parallel-safe, so either parallel-restricted or parallel-unsafe. But > if parallelModeOK is true, then it had better be parallel-restricted, > not parallel-unsafe. Ah, I see. > So I still don't see what's wrong here, other than that the comment is > evidently not half clear enough. I can get on board with that statement. Can you draft a better wording? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers