Re: Accessing schema data in information schema - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Accessing schema data in information schema
Date
Msg-id 1143124698.3985.1.camel@localhost.localdomain
Whole thread Raw
In response to Re: Accessing schema data in information schema  ("Andrew Dunstan" <andrew@dunslane.net>)
List pgsql-hackers
Ühel kenal päeval, K, 2006-03-22 kell 21:50, kirjutas Andrew Dunstan:
> Tom Lane said:
> > Darcy Buskermolen <darcy@wavefire.com> writes:
> >> On Wednesday 22 March 2006 13:11, Tom Lane wrote:
> >>> (Thinks a bit...)  Maybe it would work for pg_sequence to be a real
> >>> catalog with a row per sequence, and we also create a view named
> >>> after the sequence that simply selects from pg_sequence with an
> >>> appropriate WHERE condition.
> >
> >> I'd think that would be a workable solution, with documentation notes
> >> that  this will be deprecated in favor of information_schema  in an
> >> upcoming  release ?
> >
> > Yeah, we could consider the views a transitional thing, and get rid of
> > them after a release or two.  Tell people to change over to either look
> > in the pg_sequence catalog, or use the information_schema view.  Does
> > that view expose everything that there is, though, or will we have
> > proprietary extensions that are not in SQL2003?
> >
> 
> What happens to sequence ACLs?

perhaps we can keep pg_class part of seqs and just make the
pg_class.relfilenode to point to row oid in pg_sequence table ?

-------------
Hannu



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: pgNixInstaller: Making PostgreSQL relocatable
Next
From: "Kevin Grittner"
Date:
Subject: Re: Where does the time go?