From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | David Johnston <polobo(at)yahoo(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: psql \d+ and oid display |
Date: | 2014-03-29 20:49:01 |
Message-ID: | 20140329204901.GB30470@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 29, 2014 at 09:59:36AM -0700, David Johnston wrote:
> As my belief is that 99% of the uses of \d are for human consumption
> (because machines should in most cases hit the catalogs directly) then
> strictly displaying "Includes OIDs" when appropriate has my +1.
>
> Uses of \d+ in regression suites will be obvious and quickly fixed and
> likely account for another 0.9%.
>
> psql backslash commands are not machine API contracts and should be adapted
> for optimal human consumption; thus neutering the argument for maintaining
> backward compatibility.
One other issue --- we are adding conditional display of "Replica
Identity" to psql \d+ in 9.4, so users processing \d+ output are already
going to have to make adjustments for 9.4. That is another reason I am
asking about this now.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-03-29 21:10:49 | Re: psql \d+ and oid display |
Previous Message | Tom Lane | 2014-03-29 20:47:34 | Re: pgsql: Revert "Secure Unix-domain sockets of "make check" temporary clu |