Re: Removal of deprecated views pg_user, pg_group, pg_shadow

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removal of deprecated views pg_user, pg_group, pg_shadow
Date: 2017-02-14 03:50:43
Message-ID: CA+TgmoY2CRHJyK53kWrN6eJCk=W+=Ujx-hptCALa+=cQMdP3Hw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 13, 2017 at 5:29 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
>> On Thu, Feb 9, 2017 at 8:54 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>> > Note that these views have not been consistently maintained and have
>> > ended up including some role attributes from recent versions
>>
>> That's not a bug. According to the documentation, these views exist
>> for compatibility with PostgreSQL versions before 8.1, so there's no
>> need to update them with newer fields. Clients who are expecting to
>> talk with a pre-8.1 PostgreSQL won't expect those fields to be present
>> anyway.
>
> Yet we added bypassrls to them, after a similar discussion of how
> they're for backwards compat and we can't get rid of them, but we should
> update them with new things, blah, blah.

My recollection of that conversation is a little fuzzy and I can't
immediately find the email in the archives, but I don't think I argued
for that; I think I may have argued against it; I don't think that I
understood the point of it then and I don't now. In short, if you're
feeling under some kind of obligation to update those views, don't
feel obliged on my account.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-02-14 03:56:57 Re: REINDEX CONCURRENTLY 2.0
Previous Message Robert Haas 2017-02-14 03:45:56 Re: Parallel bitmap heap scan