Re: psql \d+ and oid display

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
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-27 20:50:43
Message-ID: 53348F23.5060505@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 03/27/2014 04:43 PM, David Johnston wrote:
> Bruce Momjian wrote
>> When we made OIDs optional, we added an oid status display to \d+:
>>
>> test=> \d+ test
>> Table "public.test"
>> Column | Type | Modifiers | Storage | Stats target | Description
>> --------+---------+-----------+---------+--------------+-------------
>> x | integer | | plain | |
>> --> Has OIDs: no
>>
>> Do we want to continue displaying that OID line, or make it optional for
>> cases where the value doesn't match default_with_oids?
> If we didn't make it behave this way at the time of the change then what has
> changed that we should make it behave this way now? I like the logic
> generally but not necessarily the change.
>
> The disadvantage of this change is users (both end and tools) of the data
> now also have to look at what the default is (or was at the time the text
> was generated) to know what a suppressed OIDs means. Given how much
> information the typical \d+ generates I would suspect that the added noise
> this introduces is quickly ignored by frequent users and not all the
> disruptive to those who use \d+ infrequently. Tools likely would prefer is
> to be always displayed.
>
>

Frankly, to me it's just useless noise.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian Pflug 2014-03-27 21:01:15 Re: [PATCH] Negative Transition Aggregate Functions (WIP)
Previous Message David Johnston 2014-03-27 20:43:51 Re: psql \d+ and oid display