| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove source code display from \df+? |
| Date: | 2023-01-12 17:06:13 |
| Message-ID: | CAMsGm5fNUVmeOfw=2MjOG4av+G2iNf5n76yj-4DsG2YCDdOAbQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 12 Jan 2023 at 10:04, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
We could shorten it to "See \sf" or something like that. But if we change
>>> the column header to "internal name" or the like, then the column just
>>> obviously doesn't apply for non-internal languages, so leaving it null
>>> should be fine.
>>>
>>
>> +1
>>
>>
> Sure, that works for me as well. I agree the suggested text was way too
> long, I was more thinking of "something in this direction" rather than that
> exact text. But yes, with a change of names, we can leave it NULL as well.
>
Thanks everybody. So based on the latest discussion I will:
1) rename the column from “Source code” to “Internal name”; and
2) change the contents to NULL except when the language (identified by oid)
is INTERNAL or C.
Patch forthcoming, I hope.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-01-12 17:12:15 | Re: Decoupling antiwraparound autovacuum from special rules around auto cancellation |
| Previous Message | Isaac Morland | 2023-01-12 17:02:37 | Re: Named Operators |