| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Any reason not to show "null input" (strict) column in \df+ output? |
| Date: | 2018-02-22 16:15:32 |
| Message-ID: | 12725.1519316132@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> The STRICT-ness of a function seems like it should be viewable when using
> \df+; is its absence just an oversight?
I've been annoyed by that in the past. I have some vague memory of
proposing adding it and being shot down, on don't-remember-what grounds.
But I couldn't find any such discussion in a quick trawl of the archives,
so maybe I'm misremembering. The only reasonable counter-argument I can
think of now is that it'd make the display Even Wider ... but \df+ long
since blew past any reasonable screen width.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pablo Liendo | 2018-02-22 18:05:24 | On error mesage (0x80090325) whilst installing Apps Stack Builder |
| Previous Message | David G. Johnston | 2018-02-22 15:57:02 | Any reason not to show "null input" (strict) column in \df+ output? |