Re: System catalog future changes

From: Erik Jones <erik(at)myemma(dot)com>
To: Steve Midgley <public(at)misuse(dot)org>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: System catalog future changes
Date: 2007-12-18 17:38:00
Message-ID: 2C8AD9F2-4891-4D96-87D1-7101A180CC79@myemma.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Dec 18, 2007, at 10:53 AM, Steve Midgley wrote:

> Hello again,
>
> Reading a previous recent post and answers called "Describe Table"
> got me thinking about a little piece of SQL I use in an application
> to get a list of all the tables for a specific namespace:
>
> select pg_class.relname as table_name
> from pg_class
> join pg_namespace on pg_namespace.oid = relnamespace
> where pg_class.relkind = 'r' and pg_namespace.nspname = 'public'
> order by pg_class.relname
>
> I have assumed that this sort of query would be relatively
> "durable" - that future system catalog changes are unlikely to make
> this query stop working? Does anyone have any knowledge of how
> "fixed" the columns and values of this query are (i.e. are there a
> lot of internal and external dependencies that make future Pg
> versiosn unlikely to break the above code)?
>
> Any other input on the above SQL - should I be doing this in
> another way?
>
> Thanks for any thoughts or advice,

If all you're looking for is regular tables, the I'd use the
pg_tables view.

Erik Jones

Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Steve Midgley 2007-12-18 19:29:15 Re: System catalog future changes
Previous Message Pavel Stehule 2007-12-18 17:36:36 Re: System catalog future changes