Re: psql \d+ and oid display - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: psql \d+ and oid display
Date
Msg-id 533736D9.1030800@dunslane.net
Whole thread Raw
In response to Re: psql \d+ and oid display  (Bruce Momjian <bruce@momjian.us>)
Responses Re: psql \d+ and oid display  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 03/29/2014 04:49 PM, Bruce Momjian wrote:
> 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.
>


I think Tom's suggestion probably has the most support, although it's 
not unanimous.

cheers

andrew



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: psql \d+ and oid display
Next
From: Jeff Janes
Date:
Subject: Re: [RFC] What should we do for reliable WAL archiving?