Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+
Date
Msg-id CAA4eK1KUP5h++hSK6eo--jx=jRJ2TTPqYYmOg=7anCm=__S_0w@mail.gmail.com
Whole thread
In response to EXCEPT TABLE - Case inconsistency for describe \d and \dRp+  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+
List pgsql-hackers
On Fri, Apr 10, 2026 at 12:43 PM Peter Smith <smithpb2250@gmail.com> wrote:
>
> Notice that that the describe publication says:
> "Tables:" and "Except tables:" (Lowercase "tables")
>
> Notice that the describe table says:
> "Publications:" and "Except Publications:"  (Uppercase "Publications")
>
> I think they should use a consistent case:
> eg1. (both lowercase) Except tables; Except publications, OR
> eg2. (bother uppercase) Except Tables; Except Publications
>

We should follow eg1. I checked few examples where we follow same
pattern as eg1:

Example-1: (See: "Tables from schemas")
 postgres=# \dRp+ pub1
                                                     Publication pub1
 Owner | All tables | All sequences | Inserts | Updates | Deletes |
Truncates | Generated columns | Via root | Description

-------+------------+---------------+---------+---------+---------+-----------+-------------------+----------+-------------
 amit  | f          | f             | t       | t       | t       | t
       | none              | f        |
Tables from schemas:
    "sch1"

Example-2: ((See: "No connections")
postgres=# create user u1 CONNECTION LIMIT 0;
CREATE ROLE
postgres=# \du u1
       List of roles
 Role name |   Attributes
-----------+----------------
 u1        | No connections

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Support EXCEPT for ALL SEQUENCES publications
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Fix slotsync worker busy loop causing repeated log messages