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 1jTI0U-0005hA-Jf for pgsql-docs@arkaria.postgresql.org; Tue, 28 Apr 2020 04:38:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jTI0T-0002yB-0W for pgsql-docs@arkaria.postgresql.org; Tue, 28 Apr 2020 04:38:05 +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 1jTI0S-0002y3-Qt for pgsql-docs@lists.postgresql.org; Tue, 28 Apr 2020 04:38:04 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jTI0Q-0003t3-MA for pgsql-docs@lists.postgresql.org; Tue, 28 Apr 2020 04:38:03 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 414605CF; Tue, 28 Apr 2020 00:38:00 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 28 Apr 2020 00:38:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=gNMgYkco8o1dEgrxQ16xwTo6odt 7fGIT4EcxbsXSdqo=; b=cIq+x6SIhmlSWVXm8Cli5kjGBBbbMC4Y9y+zBfwGSeH xCocMeXftwx2cquIuoguKfx/1XI4uMukwR9ggzpZ1621LOvHYkocVTQ9QQtFokIR 5wD9yJ91DUbNz2Up4eCXYIfRG5brOCG1RV0/8hdiOZnGferiK7K3qQguo2JgXqZs pHmfjaJWz2lG2vLMt92AG81MqvvcSZvCpssYrYPuC9XnUQ5Mln53G8P+CcJkqICV 3MKRJM57ZgTGfxJbSyefCPVo4a4DwEGVQA/DrZ53SVWQqQoMRpQAuL3bEPQ4RCIs 4OlFSZtzjoqKZqrSRDJBg07o2C9W7nlagaw7z/v3VsA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=gNMgYk co8o1dEgrxQ16xwTo6odt7fGIT4EcxbsXSdqo=; b=cWUX1TXHYyQP8fEAYJHEr/ NizNZHiG9kPA+8yz5wusMgsrK7+CgjcCiZuEIAnSYyX045jUqSOxXmtFL63Awm2p P4ZVfV7/JbLMF0A9np5uDgHeGdKznLnIEloAJYnojp4e+J2xl5UTp48PdmI4rgKV M5FwRxz/vuEHHN+D9vWze4bx1N770O/s3z0w0/qocx+mqxBmNkNwfI2NtmGeOgz3 pcVzBGWSOAwrMFmvBlluvjEO2kSDwCefbBvPrlqLsnRq4aVdYmMM6amyrrBy35bv rxrCY3KDlaC/MTGWF+26r2BhbpftjTM/o6Pus+R1sbwOvTGdcC4FKNttUt7iqQVQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedriedtgdekvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecukfhppeduuddurddutddvrddukedtrddukeehnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesph grqhhuihgvrhdrgiihii X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id 857B73065E9B; Tue, 28 Apr 2020 00:37:58 -0400 (EDT) Date: Tue, 28 Apr 2020 13:37:55 +0900 From: Michael Paquier To: Daniel Gustafsson Cc: pgsql-docs@lists.postgresql.org Subject: Re: Roles for pg_basebackup Message-ID: <20200428043755.GC279958@paquier.xyz> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tVmo9FyGdCe4F4YN" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --tVmo9FyGdCe4F4YN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Apr 27, 2020 at 12:16:41PM +0200, Daniel Gustafsson wrote: > Based on a recent conversation about backups I had I propose a small tweak to > the pg_basebackup documentation. Listing the user types in the reverse order > from today, putting superuser last, makes it IMO a little clearer that a > REPLICATION role is preferrable to using a superuser for running backups. Makes sense to me. We do that in logical-replication.sgml as well as pg_rewind.sgml (the latter outlines superuser rights last). Any objections from others? -- Michael --tVmo9FyGdCe4F4YN Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl6nsyMACgkQnvQgOdby QH3lWxAAoti++3KckKvFX7435mbup/Af+ZzOh1eG9vpy/NHyIsCnPaG32gpNxTs2 +PndubOQUstOsTuJt/caOmB/2ftLt4S88IVsFKh1M+Za6bsVG+LiJiBD0o6qT4rZ bZXMBro9N+I4ahtXxmvuwEUQxDbG0OPuSmjCl4KhAkg2wpXncShUpm+2a35dy9nS ToEKqNzylHafn8gI4JQh5z6qFSBUeOtNzsTk63mHucMeUVKYU/RdEoQ5EEM319HD Qn3B5jwVZ5Zk9GSIxi6JYBpi1dKV8sLwslraLZ4jNo3yhl9HRi2BSEsuCwdy3Awu 5bJw0fK9/kvtoxdme2wTmMz7UdgX5rL6eO7V/3ulgKyqFPK3LMVV/fyJ1m77YeOj Z4ACOA21c1pAHv9UoiDx7t0rV+uAKvqce0LEFF9bP8376CMr1uE0Rlz9wkom6Oj6 yzRyv7Dl+TWkf+vS7DEUizINv0R568zjGwABCJw61Pc9j6AMknItrhFM31MjxDo3 1SI/Emt3KtGQQVKf7jS0Aozo1jMEaG67pQtPDO4ml+AME24pWgSXJ++99ilzGBuT PlUnqs5/yMnBW8HvA5hOr1UG3ju8+1vx3q4TW+zvcCPtmmdvef6I/jJqfm2+9j+3 5fGj5pjKLS3YXvH4ELVnpVMhgycKcNhuiYSPo+SF7Iqfpr6Tj9I= =hJzQ -----END PGP SIGNATURE----- --tVmo9FyGdCe4F4YN--