From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, David Johnston <polobo(at)yahoo(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql \d+ and oid display |
Date: | 2014-04-08 21:29:45 |
Message-ID: | 28489.1396992585@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> If we ignore backward compatibility, then "Has OIDs" and "Identity
> Replica" are similar. One thing that strongly (for me) supports not
> always printing them is that I expect more people will be confused by
> the mention of OIDs or "Identity Replica" than will actually care about
> these features. For example, if we always printed "Child tables: 0",
> more people would be confused than helped.
This is a good argument, actually: these fields are not only noise for
most people, but confusing if you don't know the feature they are
talking about.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-04-08 21:34:01 | Re: Call for GIST/GIN/SP-GIST opclass documentation |
Previous Message | Bruce Momjian | 2014-04-08 21:19:09 | Re: psql \d+ and oid display |