Re: psql's \d and \dt are sending their complaints to different output files

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql's \d and \dt are sending their complaints to different output files
Date: 2017-06-19 15:09:19
Message-ID: CAFiTN-tFQmWrqcJDGVNtF+DMds32fwaWyUfwGf9GOwHrPSOLpA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 19, 2017 at 6:30 PM, Oleksandr Shulgin
<oleksandr(dot)shulgin(at)zalando(dot)de> wrote:
> I think can be helpful, though rarely, to be able to send the output of \d*
> commands to a file. At the same time it would be nice to see the message on
> stderr instead of appending to the output file, in case the relation was not
> found, because of less head-scratching needed to realize the problem. So
> I'd vote for changing \dt (and alike) behavior to use stderr.

+1

And, we can also change the error message to be more consistent.

\d says "Did not find any relation named "xxx" ". whereas \dt says "No
matching relations found".

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-06-19 15:32:20 Re: psql's \d and \dt are sending their complaints to different output files
Previous Message Tom Lane 2017-06-19 15:09:18 Re: BUG: pg_dump generates corrupted gzip file in Windows