Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 9C66E2E2D85 for ; Tue, 18 Dec 2007 15:29:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 79155-01 for ; Tue, 18 Dec 2007 15:29:50 -0400 (AST) Received: from starfish.geekisp.com (mail.geekisp.com [216.168.135.169]) by postgresql.org (Postfix) with ESMTP id 704342E35A2 for ; Tue, 18 Dec 2007 15:29:48 -0400 (AST) Received: (qmail 21035 invoked by uid 1003); 18 Dec 2007 19:30:26 -0000 Received: from adsl-67-124-150-42.dsl.pltn13.pacbell.net (HELO dino-1.misuse.org) (public@misuse.org@67.124.150.42) by mail.geekisp.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 18 Dec 2007 19:30:26 -0000 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 18 Dec 2007 11:29:15 -0800 To: pgsql-sql@postgresql.org From: Steve Midgley Subject: Re: System catalog future changes In-Reply-To: <2C8AD9F2-4891-4D96-87D1-7101A180CC79@myemma.com> References: <20071218165836.4EFD42E004C@postgresql.org> <2C8AD9F2-4891-4D96-87D1-7101A180CC79@myemma.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Message-Id: <20071218192948.704342E35A2@postgresql.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/101 X-Sequence-Number: 29793 Thanks Erik - that cleans things up significantly for me. For the record, the SQL for finding all the table=20 names (alpha ordered) in the public schema using pg_tables view is: select tablename from pg_tables where=20 schemaname=3D'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 =3D relnamespace >>where pg_class.relkind =3D 'r' and pg_namespace.nspname =3D '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=AE >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 > > >