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 1knpgW-0003fc-49 for pgsql-admin@arkaria.postgresql.org; Fri, 11 Dec 2020 21:10:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1knpgU-0000Wn-Un for pgsql-admin@arkaria.postgresql.org; Fri, 11 Dec 2020 21:10:38 +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 1knpgU-0000Wg-NE for pgsql-admin@lists.postgresql.org; Fri, 11 Dec 2020 21:10:38 +0000 Received: from tamriel.snowman.net ([70.109.60.50]) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1knpgO-0002vy-4J for pgsql-admin@lists.postgresql.org; Fri, 11 Dec 2020 21:10:37 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 76E025F799; Fri, 11 Dec 2020 16:10:31 -0500 (EST) Date: Fri, 11 Dec 2020 16:10:31 -0500 From: Stephen Frost To: Scott Ribe Cc: Tom Lane , Pgsql-admin Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate Message-ID: <20201211211031.GC16415@tamriel.snowman.net> References: <20201211203634.GB16415@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="KjLXavu97SsPN3hE" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --KjLXavu97SsPN3hE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Scott Ribe (scott_ribe@elevated-dev.com) wrote: > > On Dec 11, 2020, at 1:36 PM, Stephen Frost wrote: > > I'm pretty sure none of this has anything to do with DEFAULT PRIVILEGES > > as those only actually apply when a new table is created (and not from a > > template database), and that's just never the case with any PG catalog > > tables. >=20 > So the fact that default privs were set on the system catalogs was inappr= opriate, but harmless in this case? Almost certainly. > > What might be useful to point out is that only a superuser can change > > the privileges associated with PG catalog tables and that you really > > should be careful who you grant superuser privileges to. >=20 > Yes, that's one thing I took care of earlier this year: change our proces= ses such that we were able to remove superuser from the commonly-used servi= ce accounts. =2E.. and hopefully from most every other account. There's really very little need to have actual superuser rights (something we continue to work to limit the need of with each release). Thanks, Stephen --KjLXavu97SsPN3hE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJf0+BHAAoJEO1sijiDR2RVJccP/36IQl6Spx/Hh1b/qpRIL3Nd l88dZINeUo55cSMYqA5zSBXVwfNeWW0+kl3AnmWwiumLmlRVd+7ktI5t6HvdmDgi O7tNJut9XB1rtwesUuYZwm1k48KTuc8N5+I8Q3NLqsSusOm7gAslL6wTnTUfpolJ 7YA+NBOZK5vqI2rQQTdD9Igi7mWNwpPZmdkogjXfeqysKwdYf8kyMlgEv86uZ3jz 5u80N7u4zDJvX5eFIi55Qhy1p5K7RdzY6RTSab7TT/XO9OOm3mcCwZrUDzkFMS6J FmmcG3uz3KlDXKBTv3YNlXwJr5cJ0LePuBZWzqmwDhw2pTN/LJp6mpT3GVtaeLQJ SRezXVANG6eqlV9xbMHPDKsz8+oEXYj7zy85ChHJ1gbjIbGFyxX6s3LFeeBN9zOP SQur/aifSyeeBgLFnFDiM9orrz2TVApUtpZuAkDv4WGOrpOsgvxFeo8iSq9+NJYX vfo3hmMy/DKocqjkGWOoaiwulgvCRF7G/uEBkFtt6znwU6qoa7LudFaJRhb+3VhV NYh5HDosvTC777K+bTtx2KpXp5ed2VktF0mXlOjfT+7KLyPts7hyXGZTyptWgQDn RVN12mw3yOn9wRwYgAMTA/leol7ZWx3SwD7o6oRRMSuJT4bUVx+MFP6gvQ1zi9Z9 m80MpqrDpPwMqoDilM1x =1cgy -----END PGP SIGNATURE----- --KjLXavu97SsPN3hE--