Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YUFeq-0007hi-N2 for pgsql-hackers@arkaria.postgresql.org; Sat, 07 Mar 2015 14:24:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YUFeq-0008UC-1v for pgsql-hackers@arkaria.postgresql.org; Sat, 07 Mar 2015 14:24:48 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YUFeo-0008U5-Lm for pgsql-hackers@postgresql.org; Sat, 07 Mar 2015 14:24:46 +0000 Received: from tamriel.snowman.net ([2001:4830:167b::11]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YUFel-0003XS-DY for pgsql-hackers@postgresql.org; Sat, 07 Mar 2015 14:24:44 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id B141C5F7A3; Sat, 7 Mar 2015 09:24:41 -0500 (EST) Date: Sat, 7 Mar 2015 09:24:41 -0500 From: Stephen Frost To: Peter Eisentraut Cc: Tom Lane , Adam Brightwell , Noah Misch , PostgreSQL Hackers Subject: Re: CATUPDATE confusion? Message-ID: <20150307142441.GD29780@tamriel.snowman.net> References: <20141227080926.GA2035611@tornado.leadboat.com> <20141227151034.GU3062@tamriel.snowman.net> <28382.1419703324@sss.pgh.pa.us> <20141227231829.GX3062@tamriel.snowman.net> <1952.1419722762@sss.pgh.pa.us> <20141227233150.GA2046947@tornado.leadboat.com> <54FA8203.8080709@gmx.net> <4593.1425706263@sss.pgh.pa.us> <54FB0708.7070200@gmx.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="K+ePCyV5oXUTN8MZ" Content-Disposition: inline In-Reply-To: <54FB0708.7070200@gmx.net> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/3.13.0-45-generic (x86_64) X-Uptime: 09:12:28 up 44 days, 14:01, 15 users, load average: 0.23, 0.20, 0.19 User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org --K+ePCyV5oXUTN8MZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Peter Eisentraut (peter_e@gmx.net) wrote: > On 3/7/15 12:31 AM, Tom Lane wrote: > > Peter Eisentraut writes: > >> On 12/29/14 7:16 PM, Adam Brightwell wrote: > >>> Given this discussion, I have attached a patch that removes CATUPDATE > >>> for review/discussion. > >=20 > >> committed this version > >=20 > > Hmm .. I'm not sure that summarily removing usecatupd from those three > > system views was well thought out. pg_shadow, especially, has no reason > > to live at all except for backwards compatibility, and clients might we= ll > > expect that column to still be there. I wonder if we'd not be better o= ff > > to keep the column in the views but have it read from rolsuper. >=20 > I doubt anyone is reading the column. And if they are, they should stop. Certainly pgAdmin and similar tools are. From that standpoint though, I agree that they should be modified to no longer read it, as the whole point of those kinds of tools is to allow users to modify those attributes and having CATUPDATE in the view would surely be confusing as the user wouldn't be able to modify it. > pg_shadow and pg_user have been kept around because it is plausible that > a lot of tools want to have a list of users, and requiring all of them > to change to pg_authid at once was deemed too onerous at the time. I > don't think this requires us to keep all the details the same forever. pg_shadow, pg_user and pg_group were added when role support was added, specifically for backwards compatibility. I don't believe there was ever discussion about keeping them because filtering pg_roles based on rolcanlogin was too onerous. That said, we already decided recently that we wanted to keep them updated to match the actual attributes available (note that the replication role attribute modified those views) and I think that makes sense on the removal side as well as the new-attribute side. I continue to feel that we really should officially deprecate those views as I don't think they're actually all that useful any more and maintaining them ends up bringing up all these questions, discussion, and ends up being largely busy-work if no one really uses them. Thanks, Stephen --K+ePCyV5oXUTN8MZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJU+wopAAoJEO1sijiDR2RVDtgP/35LLX5kj82HTQ6NEIjtnK6m No6jxLZkKscXQ5goyrjvrHqqICdJUai8x3wMGxsqrpUAPctsjiJWCwTVpJcImNV6 exWs6fOLdVKY35fWGxmH5bc/DtmV8DE9IW1uFwsvMInIiVl8qBUQHK3nR9mwYpzP ec6zU5gypsNVvUT/xfskax4eNqSnTakG8G9lHWC2e3Yife0j67JEE+jeOfT65dgu tFUIXSgfVYA6Zb+9WGR1v46r/TkT54rZBnGM9o5jpWIogy5zZu0kMy+j0MrHJYau 6cNLFQ0Zqr1Q9g2dBEAloVSC0v/xkSl2oBAQ67J6sD0ZunNY1z/qDJTcFep2ls1B uTRqq5K4scWanOR6xOalpbaueLD63VBn9/9g9MKkpv14SesDaYpMBVGEOiyIxyE4 3kHbXgbszdJVrPoXmsZWaFhy+XDR/NpMynsRq7P+iqitQAemRquWTLPkvAacs/uc gnFXeX+pHTv4L5QD11u+Az8cXkNO7FRSb4cW7EvFR4VgGWlNiqKGwk3OSMCweH4B RolPWQKLbWvU7WG8mxgpYTnxjlgc7yYvPUpBPUZX50hfcHzCEI7GL3dJih3jShHV GPMjy0B3SkIX6TZ2E26dEzHtCD0gVzA9JXqkvMYRGHhNesENGsyBTACvKA0DklDa r9p7f7OCv1ECX56TilGV =7V6H -----END PGP SIGNATURE----- --K+ePCyV5oXUTN8MZ--