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 1oqcTj-0008Qs-1x for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Nov 2022 15:50:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oqcTi-0005KM-0B for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Nov 2022 15:50:02 +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 1oqcTg-0005Ca-UV for pgsql-hackers@lists.postgresql.org; Thu, 03 Nov 2022 15:50:01 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oqcTc-0005tg-6J for pgsql-hackers@lists.postgresql.org; Thu, 03 Nov 2022 15:50:00 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D10A75C0213; Thu, 3 Nov 2022 11:49:53 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 03 Nov 2022 11:49:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1667490593; x= 1667576993; bh=S1wj5Xhkv2tLyH5plAfcxAzjYb0XzyNt1GvLMmtUJvI=; b=g ueTreNb2vp8OCxPCK+jViCDGIGZxxNcY0JhYBjv2/DFXtq/Fot8sgbzo4O/zcDF5 7jyR74KjYeVM9Xs9xSKLDo83BeUBZKA27FiDC97pZq7j+pmyaZZB5U3kNpbwBbQS N/eY01Cgr/+DGu9GsajiVg682e83sg5S2cvh6sFxgkWxeF0K7ivcw8rUBq7wPtgV Y0UMnxQKpPIiIpUnzbcDoU+Twwh0UA3oZizO/nH/l7w35mUFLF08hmPTA3teJsuU DP3aTnxblKll2zk1N80SgQ8OZZ1KZRdxDyGkkKYGjE2hncz30OpJe0MCwrNBR0HZ BTBrMmCcHEafdOCQbritA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrudelgdejhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepvdevjefgjeefheefueeu keduleffhfejjedttdelveeiffduvdeggfetveejhfelnecuffhomhgrihhnpehpohhsth hgrhgvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvug gsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 3 Nov 2022 11:49:52 -0400 (EDT) Message-ID: Date: Thu, 3 Nov 2022 11:49:51 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Subject: Re: Privileges on PUBLICATION Content-Language: en-US To: Antonin Houska Cc: Euler Taveira , Amit Kapila , PostgreSQL Hackers References: <20330.1652105397@antos> <8a00e0e1-dc4e-422c-9dcf-664b16b18625@www.fastmail.com> <2810.1652171844@antos> <5859.1652423797@antos> <57022.1652867097@antos> <4c420c17-8570-4b52-b7f6-9ce3f53d7ef9@www.fastmail.com> <14292.1655733695@antos.home> <746c9a65-e2cc-2573-a50e-ab5ea884f680@enterprisedb.com> <1537.1667454192@antos> From: Peter Eisentraut In-Reply-To: <1537.1667454192@antos> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 03.11.22 01:43, Antonin Houska wrote: > Peter Eisentraut wrote: > >> The CF entry is about privileges on publications. Please rebase that patch >> and repost it so that the CF app and the CF bot are up to date. > > The rebased patch (with regression tests added) is attached here. Some preliminary discussion: What is the upgrade strategy? I suppose the options are either that publications have a default acl that makes them publicly accessible, thus preserving the existing behavior by default, or pg_dump would need to create additional GRANT statements when upgrading from pre-PG16. I don't see anything like either of these mentioned in the patch. What is your plan? You might be interested in this patch, which relates to yours: https://commitfest.postgresql.org/40/3955/ Looking at your patch, I would also like to find a way to refactor away the ExecGrant_Publication() function. I'll think about that. I think you should add some tests under src/test/regress/ for the new GRANT and REVOKE statements, just to have some basic coverage that it works. sql/publication.sql would be appropriate, I think.