Re: Removal of deprecated views pg_user, pg_group, pg_shadow

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removal of deprecated views pg_user, pg_group, pg_shadow
Date: 2017-02-13 02:43:28
Message-ID: e28b33fc-8a3d-d4c8-e995-2b5f0e0fe3c4@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/10/17 12:04 AM, Stephen Frost wrote:
> They're misleading by having an arbitrary subset of the role attributes
> and implying that the role relationships are simpler than they actually
> are. Frankly, they're also not being consistently maintained based on
> any proper policy, which I find quite objectionable.

+1

> Of course, we could fix these issues- we could add the grantor to the
> pg_groups view, and perhaps even change it to be an acyclic directed
> graph structure, and we could add the role attributes to pg_user and
> pg_shadow which are missing, but at that point all we're really doing,
> it seems to me, is providing synonyms for the existing canonical views,
> and that hardly seems useful.

Well, there's always the issue of breaking peoples existing code, which
will probably remain an issue until we become more "in your face" with
users about stuff we're trying to deprecate.

My vote would be to either kill the views or explicitly deprecate them
and move them to contrib.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2017-02-13 02:58:26 Re: drop support for Python 2.3
Previous Message Tomas Vondra 2017-02-13 02:41:55 Re: Checksums by default?