Re: Extending System Views: proposal for 8.1/8.2 - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Extending System Views: proposal for 8.1/8.2
Date
Msg-id 200501231216.31607.josh@agliodbs.com
Whole thread Raw
In response to Re: Extending System Views: proposal for 8.1/8.2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Extending System Views: proposal for 8.1/8.2  ("Marc G. Fournier" <scrappy@postgresql.org>)
Re: Extending System Views: proposal for 8.1/8.2  (Yann Michel <yann-postgresql@spline.de>)
List pgsql-hackers
Tom,

> Any new schemas introduced by PG itself will be named pg_something.
> This is not open to negotiation --- it's what we've promised to users
> to avoid tromping on their schema namespace.

I can see the sense in that.  So, there's four ways I can see to do things:

1) leave the existing views (pg_tables, pg_views, etc.) the way they are 
except for adding columns.   Create new views based on the naming scheme of 
the old.

2) create new views in pg_catalog, using new names.  The problem with this is 
that the most intuitive names (pg_tables, pg_views) are taken by the old 
views and I'm not sure what to name the new ones.

3) create a new schema with the system views in it, called for example 
pg_system_views.   This seems cluttered to me; a whole new schema just for a 
dozen views?  

4) ignore backwards compatibility and just re-write the old views.   I can 
hear the shouting already ...

So, a choice of annoying options.   Does anyone else on the channel have 
opinions?

-- 
Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] Merge pg_shadow && pg_group -- UNTESTED
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Extending System Views: proposal for 8.1/8.2