Re: [HACKERS] Removal of deprecated views pg_user, pg_group,pg_shadow - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] Removal of deprecated views pg_user, pg_group,pg_shadow
Date
Msg-id 20170213194208.amuasnf3dd3nko6v@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] Removal of deprecated views pg_user, pg_group, pg_shadow  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Removal of deprecated views pg_user, pg_group, pg_shadow  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas wrote:

> My big objection to removing these views is that it will break pgAdmin
> 3, which uses all three of these views.  I understand that the pgAdmin
> community is now moving away from pgAdmin 3 and toward pgAdmin 4, but
> I bet that pgAdmin 3 still has significant usage and will continue to
> have significant usage for at least a year or three.  When it's
> thoroughly dead, then I think we can go ahead and do this, unless
> there are other really important tools still depending on those views,
> but it's only been 3 months since the final pgAdmin 3 release.

Well, we can remove them from PG10 and pgAdmin3 (and others) be adjusted
to use the new ones, conditionally on server version.  Surely pgAdmin3
is going to receive further updates, given that it's still widely used?

> IMHO, these views aren't costing us much.  It'd be nice to get rid of
> them eventually but a view definition doesn't really need much
> maintenance.

Maybe not, but the fact that they convey misleading information is bad.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [HACKERS] Removal of deprecated views pg_user, pg_group,pg_shadow
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] possibility to specify template database for pg_regress