Re: psql's \dn versus temp schemas - Mailing list pgsql-hackers

From Tom Lane
Subject Re: psql's \dn versus temp schemas
Date
Msg-id 22630.1285353739@sss.pgh.pa.us
Whole thread Raw
In response to Re: psql's \dn versus temp schemas  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: psql's \dn versus temp schemas  (Dimitri Fontaine <dfontaine@hi-media.com>)
Re: psql's \dn versus temp schemas  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On sön, 2010-09-19 at 13:51 -0400, Tom Lane wrote:
>> Hmm.  If we had a \dnS option, what I would sorta expect it to do is
>> show the "system" schemas pg_catalog and information_schema.  The
>> toast
>> and temp schemas seem like a different category somehow.  On the other
>> hand, if we did it like this, then the S and + modifiers would be
>> orthogonal which is a nice property.

> Well, normally the + option shows more columns and the S option shows
> more rows.  Showing more "internal" objects with + might be a bit
> confusing.

Okay, it seems to be the consensus that \dn should have orthogonal
S and + options (S = show system stuff, + = show more columns).

How do we want to define "system" exactly?  My original proposal was
for bare \dn to hide the temp and toast schemas.  If we consider that
what it's hiding is "system" schemas then there's some merit to the
idea that it should hide pg_catalog and information_schema too.
In that case, in a fresh database you would *only* see "public".
I'm not sure that I like this though.  Comments?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: History for 8.3.6 tag is a little strange
Next
From: Tom Lane
Date:
Subject: Re: History for 8.3.6 tag is a little strange