Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] psql's \d and \dt are sending their complaints todifferent output files - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: [HACKERS] psql's \d and \dt are sending their complaints todifferent output files
Date
Msg-id CAFiTN-tFQmWrqcJDGVNtF+DMds32fwaWyUfwGf9GOwHrPSOLpA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] psql's \d and \dt are sending their complaints to different output files  (Oleksandr Shulgin <oleksandr.shulgin@zalando.de>)
Responses Re: [HACKERS] psql's \d and \dt are sending their complaints to different output files
List pgsql-hackers
Tree view 
On Mon, Jun 19, 2017 at 6:30 PM, Oleksandr Shulgin
<oleksandr.shulgin@zalando.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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] BUG: pg_dump generates corrupted gzip file in Windows
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] psql's \d and \dt are sending their complaints to different output files