Re: psql's \dn versus temp schemas

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql's \dn versus temp schemas
Date: 2010-09-24 18:42:19
Message-ID: 22630.1285353739@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On sn, 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-09-24 19:06:42 Re: History for 8.3.6 tag is a little strange
Previous Message Jeff Davis 2010-09-24 18:36:06 History for 8.3.6 tag is a little strange