X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 8888F9FA5E6 for ; Fri, 9 Jun 2006 18:00:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 84780-10 for ; Fri, 9 Jun 2006 18:00:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id DC3F19FA1A8 for ; Fri, 9 Jun 2006 18:00:03 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 9D0BF5647F; Fri, 9 Jun 2006 16:00:02 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Fri, 9 Jun 2006 16:00:01 -0500 Date: Fri, 9 Jun 2006 16:00:01 -0500 From: "Jim C. Nasby" To: Tom Lane Cc: pgsql-hackers@postgresql.org Subject: Re: List schema contents Message-ID: <20060609210000.GJ57289@pervasive.com> References: <20060609193356.GC57289@pervasive.com> <24470.1149884416@sss.pgh.pa.us> <20060609202741.GF57289@pervasive.com> <24709.1149886507@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <24709.1149886507@sss.pgh.pa.us> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060609:tgl@sss.pgh.pa.us::3QS9NgnuP/RlqgAp:00000000000000000000 0000000000000000000000005RDp X-Hashcash: 1:20:060609:pgsql-hackers@postgresql.org::rCyf0CoYFtFTrlZD:000000000 000000000000000000000000C5xD X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/469 X-Sequence-Number: 84702 On Fri, Jun 09, 2006 at 04:55:07PM -0400, Tom Lane wrote: > "Jim C. Nasby" writes: > > What I'm looking for is what "\d" provides you, only limited to a > > specific schema. "\d information_schema." (for example) doesn't provide > > that; it provides the details for every table/view in > > information_schema. > > What you're looking for is \dt, or perhaps \dtsv or one of those forms. \dtsv produces exactly what I'd want/expect. > I'd be the first to agree that the behavior of \d isn't particularly > orthogonal, but it's not the pattern language that's the problem, it's > the command itself. Perhaps \d without an argument should just do whatever \dtsv does? -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461