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 1mnPzK-0000S6-PQ for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Nov 2021 18:48:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mnPzJ-0007gv-Ew for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Nov 2021 18:48:53 +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 1mnPzJ-0007gl-5X for pgsql-hackers@lists.postgresql.org; Wed, 17 Nov 2021 18:48:53 +0000 Received: from mail-pl1-x62c.google.com ([2607:f8b0:4864:20::62c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mnPzE-0002L5-Vt for pgsql-hackers@postgresql.org; Wed, 17 Nov 2021 18:48:52 +0000 Received: by mail-pl1-x62c.google.com with SMTP id b13so2995225plg.2 for ; Wed, 17 Nov 2021 10:48:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YYvLeZw9lXSfcCXTCdFFnYK3+cWPrDoptWrrnZ2F95A=; b=AjpDhntGmRCpW29hjoqED4ixv0ETv464KNruj8ejlnUBAZajctBA8RVHqDOioVgVs3 ugqpCZcivRidC4/pUEaFZoD7MHK+KdB6fKVi3rMqeGJDOxGlVm3JQdfFG1BVk1Yz5lqN f8/KSXR/8qOpnhUrG0Odfy4K72MxFRffMFAfJdoKC0Fq0cUSCn4FsiXtGrEk25SVjGkn JAvTBq8ahw+zgNo7MpddGn8z9YKNbx0nnIlvF2FJahoM1IgfWi+NPnCmyri2MwEzdCdF g43zBJny+LVkqwsFQ6w/KNE7pWa2Dx2t8pKX92X2w0VvAFf+f0Tq6d6gYHfMIipBDapE ODDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YYvLeZw9lXSfcCXTCdFFnYK3+cWPrDoptWrrnZ2F95A=; b=6FQf7FV5PHdWAuL/n82GSFgeECiyn9IQXhJHs0vHDhBhCmMku1X0j+5N/uqG5GYEJj P2Qv40Ec/7F2UA35ioDBn78yIDloBs4usTDiW425H/ArTvDoN8IhwC30ad+BZveANuAk yfiE2NKvXgA/ZUuy3aVbnuBbNgd0Sf3T7HOhS7n5fXAGaX2GG1Z5goUxpl6Uy1bHaAR3 L/QdLiFMCc8A8TiMr5vlrBJvxxNuMAE73Eu4prAoT1QRXC6UpyAYvMFmSKuDpdI+f7am LUW3XbgsriZ3ZkP6Fn2g8i1fVVdn/Uz33Lsj1tzwERlgTw/Yd2qqzLtFHkT+8xAG3ref 1Dpw== X-Gm-Message-State: AOAM530IBx4WBgyNylnYvuBTvI7GoZPG7ZweaepkOjj948Y2/Z5hAUqs RTSK9I7JPZDzLGb8hd3wcO6Ig5vlfZbLr+bbmnL6e1XkZmKT76wWRJAqO7tRmLvtfrka91L/6mI rCKZnwo2IIVgaw/a1F5V97RufVgSetPpC31TBMhYOPiMHA9/SsHljExkyWu55N3rE7EVuC4pBDN rpzZOj+Zit4YLceXQ5Y8bL5lRuW5A8oab7rYSC X-Google-Smtp-Source: ABdhPJz9d4Loro2bYHESgXrf6wcjybXkE2cb6AiZF8UJXjuEeASg8FwwgXTys8ZjjotZJy1vML6JOw== X-Received: by 2002:a17:90a:1bc5:: with SMTP id r5mr2340319pjr.90.1637174926534; Wed, 17 Nov 2021 10:48:46 -0800 (PST) Received: from laptop280-ma-us.hitronhub.home (24-113-193-150.wavecable.com. [24.113.193.150]) by smtp.gmail.com with ESMTPSA id w19sm341510pjh.10.2021.11.17.10.48.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Nov 2021 10:48:46 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Re: Non-superuser subscription owners From: Mark Dilger In-Reply-To: Date: Wed, 17 Nov 2021 10:48:44 -0800 Cc: Andrew Dunstan , PostgreSQL-development , Robert Haas Content-Transfer-Encoding: quoted-printable Message-Id: References: <9DFC88D3-1300-4DE8-ACBC-4CEF84399A53@enterprisedb.com> <6BB4451E-7B1B-474C-BD1F-DB7531E720C6@enterprisedb.com> <6A2B0FF6-CC86-48CE-B0D3-5401AA5CFEA9@enterprisedb.com> To: Jeff Davis X-Mailer: Apple Mail (2.3608.120.23.2.7) X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Nov 17, 2021, at 9:33 AM, Jeff Davis wrote: >=20 > Is GRANT a better fit here? That would allow more than one user to > REFRESH, or ENABLE/DISABLE the same subscription. It wouldn't allow > RENAME, but I don't see why we'd separate privileges for > CREATE/DROP/RENAME anyway. I don't think I answered this directly in my last reply. GRANT *might* be part of some solution, but it is unclear to me how best = to do it. The various configuration parameters on subscriptions entail = different security concerns. We might take a fine-grained approach and = create a predefined role for each, or we might take a course-grained = approach and create a single pg_manage_subscriptions role which can set = any parameter on any subscription, or maybe just parameters on = subscriptions that the role also owns, or we might do something else, = like burn some privilege bits and define new privileges that can be = granted per subscription rather than globally. (I think that last one = is a non-starter, but just mention it as an example of another = approach.) =E2=80=94 Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company