From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris BSomething <xpusostomos@gmail.com>
Cc: PostgreSQL Bug List <pgsql-bugs@lists.postgresql.org>
Subject: Re: Bug in psql
Date: Sun, 02 Feb 2025 21:35:26 -0500
Message-ID: <292236.1738550126@sss.pgh.pa.us> (raw)
In-Reply-To: <CADrHaBF91oNdNe1JUP6-L+KnRtj_o_C-V63KEo5o4Uufdr2KzQ@mail.gmail.com>
References: <CADrHaBEVSYwemoJWtry2+82KHy9tZirH2PVfi-uD96R5J8FCsw@mail.gmail.com>
<CAKFQuwYawZ=80oP4P8qDWA-YxtKQK_QVnVvH-OQE25benc9SQQ@mail.gmail.com>
<CADrHaBF91oNdNe1JUP6-L+KnRtj_o_C-V63KEo5o4Uufdr2KzQ@mail.gmail.com>
Chris BSomething <xpusostomos@gmail.com> writes:
> On Mon, 3 Feb 2025 at 04:36, David G. Johnston <david.g.johnston@gmail.com>
> wrote:
>> Since \d can only show information limited to the super-class relation,
>> and not specific subtypes, the information for the foreign table subtype
>> needs to be made available somewhere. That place is \det
> I don't know what that means, but when two menu items have the same text,
> but a different function, Houston, we have a problem.
It could be argued that at the level of detail that's possible in this
help summary, their functions *are* the same. The family of commands
that includes \dE will show you Schema, Name, Type, Owner, which are
properties that all relations have so they are sensible to show in a
list that might include any type of relation. On the other hand,
\det shows Schema, Table, Server (and \det+ includes FDW options),
so it is only applicable to foreign tables. But we don't have the
space in \h output to go into the specific output columns. That's
pretty much left to the user to discover by trying things.
Having said that, if you have concrete ideas about how to make the
help output clearer, let's hear them. (I'm pretty sure we've
rearranged \h's explanation of the \dtisv family before, so it's
not like this text is set in stone.) But "this is a bug and
somebody else should fix it" is not going to cause anything to
happen, mainly because it's not very clear what would be better.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, xpusostomos@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Bug in psql
In-Reply-To: <292236.1738550126@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox