Daniel Gustafsson <dan...@yesql.se> writes: > On 27 Jul 2017, at 19:40, Tom Lane <t...@sss.pgh.pa.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 -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers