From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, 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-07-28 21:46:43 |
Message-ID: | 19294.1501278403@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> On 27 Jul 2017, at 19:40, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> listTables and listDbRoleSettings print a custom message rather than
>> an empty table for no matches (but in QUIET mode they just do the
>> latter). I think that's actually a good decision for listDbRoleSettings,
>> because the user might be confused about which pattern is which, and
>> we can straighten him out with a custom error message. But the only
>> good argument for listTables behaving that way is that people are used
>> to it.
> Which is a pretty good argument for not changing it.
Yeah, not hearing any votes for changing it, I'll leave it be.
>> I'm not sure about this one. It definitely seems bogus that \dRp+ is
>> omitting the owner column, but I'm less excited about duplicating the
>> pubname.
> It’s indeed a bit silly to duplicate the information like that.
The minimum change here seems to be to add the owner column, so I did
that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-07-28 23:32:34 | In-place index updates and HOT (Was: Patch: Write Amplification Reduction Method (WARM)) |
Previous Message | Robert Haas | 2017-07-28 21:25:07 | Re: Adding support for Default partition in partitioning |