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 1pMd42-0000jl-AD for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Jan 2023 22:55:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pMd40-00060N-2u for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Jan 2023 22:55:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMd3z-0005zt-P6 for pgsql-hackers@lists.postgresql.org; Mon, 30 Jan 2023 22:55:47 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMd3x-0006tt-Gi for pgsql-hackers@lists.postgresql.org; Mon, 30 Jan 2023 22:55:46 +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 30UMthQh966589; Mon, 30 Jan 2023 17:55:43 -0500 From: Tom Lane To: Peter Smith cc: Zheng Li , pgsql-hackers@lists.postgresql.org Subject: Re: pub/sub - specifying optional parameters without values. In-reply-to: References: <167328582545.1136.8620247763467087383.pgcf@coridan.postgresql.org> <359467.1675028199@sss.pgh.pa.us> <501328.1675098031@sss.pgh.pa.us> Comments: In-reply-to Peter Smith message dated "Tue, 31 Jan 2023 09:36:53 +1100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <966587.1675119343.1@sss.pgh.pa.us> Date: Mon, 30 Jan 2023 17:55:43 -0500 Message-ID: <966588.1675119343@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Smith writes: > I'd forgotten about the 'streaming' option -- AFAIK this was > previously a boolean parameter and so its [= value] part can also be > omitted. However, in PG16 streaming became an enum type > (on/off/parallel), and the value can still be omitted but that is not > really being covered by the new generic text note about booleans added > by yesterday's patch. Hmph. I generally think that options defined like this (it's a boolean, except it isn't) are a bad idea, and would prefer to see that API rethought while we still can. regards, tom lane