Skip site navigation (1) Skip section navigation (2)

Re: psql \d* and system objects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql \d* and system objects
Date: 2009-03-30 14:29:15
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> That still has the problem that "\df a*" is horribly inconsistent with
> "\df".  It might be reasonable to assume that if a name without
> wildcards is given to any \d command, it should display whatever
> object it finds, user or system - but I can't see doing it for any
> wildcard at all.

Why not?  Seems "horribly inconsistent" to me to treat those cases

It seems entirely explainable to me to say that "if you specify
no pattern, the default behavior is to list all non-system functions".
Where the patch went wrong is in fooling with the behavior when a
pattern is specified.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2009-03-30 14:29:25
Subject: Re: PQinitSSL broken in some use casesf
Previous:From: Robert HaasDate: 2009-03-30 14:25:41
Subject: Re: psql \d* and system objects

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group