> > I think the original complaint was misguided and we should not do
> > anything about it. IIRC the complaint amounted to "I have
> > hundreds of schemas and it annoys me that \dn shows them all".
> > How is this different from putting hundreds of tables into one
> > schema and then being annoyed because \dt shows them all? We have
> > other mechanisms available for making \dn selective (ie, you can
> > use a name pattern). If \dn is restricted to showing only schemas
> > in your search path, it will become useless.
> I completely agree. It's like saying that \l should only show
> databases you are currently connected to...
For the record and if Tom was referring to me, the example I gave was
to have \dn show all schemas that you have any permissions for, not
that were in the search path. -sc
In response to
pgsql-hackers by date
|Next:||From: Marc G. Fournier||Date: 2003-12-22 04:14:57|
|Subject: 7.4.1 tag'd and bundled ...|
|Previous:||From: Andrew Dunstan||Date: 2003-12-22 01:45:11|
|Subject: Re: [pgsql-advocacy] PostgreSQL speakers needed for OSCON|
pgsql-patches by date
|Next:||From: Christopher Kings-Lynne||Date: 2003-12-22 06:21:59|
|Subject: cascading column drop to index predicates|
|Previous:||From: My Deja||Date: 2003-12-21 22:50:38|
|Subject: pgAdmin crashes when client_min_messages is set in postgresql.conf|