From: Steve Midgley <public@misuse.org>
To: pgsql-sql@postgresql.org
Subject: Re: System catalog future changes
Date: Tue, 18 Dec 2007 11:29:15 -0800
Message-ID: <20071218192948.704342E35A2@postgresql.org> (raw)
In-Reply-To: <2C8AD9F2-4891-4D96-87D1-7101A180CC79@myemma.com>
References: <20071218165836.4EFD42E004C@postgresql.org>
<2C8AD9F2-4891-4D96-87D1-7101A180CC79@myemma.com>
Thanks Erik - that cleans things up significantly for me.
For the record, the SQL for finding all the table
names (alpha ordered) in the public schema using pg_tables view is:
select tablename from pg_tables where
schemaname='public' order by tablename
Steve
At 09:38 AM 12/18/2007, Erik Jones wrote:
>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@myemma.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
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: public@misuse.org
Subject: Re: System catalog future changes
In-Reply-To: <20071218192948.704342E35A2@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox