| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, turon(dot)david(at)seznam(dot)cz |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16743: psql doesn't show whole expression in stored column |
| Date: | 2020-11-25 08:38:03 |
| Message-ID: | 7a1faa2c-d4d1-67fd-03fe-29ef7e240301@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2020-11-24 16:46, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
>> when generated column expression length is larger then some value - the rest
>> of expression is cut in \d[+] output:
>
> Yeah, this is an intentional and very ancient behavior:
>
> appendPQExpBufferStr(&buf,
> ",\n (SELECT substring(pg_catalog.pg_get_expr(d.adbin, d.adrelid, true) for 128)"
> "\n FROM pg_catalog.pg_attrdef d"
>
> Maybe we should decide that completeness is more important than keeping
> the line to some arbitrary width. But it's operating as designed.
I think we should get rid of the truncating. Otherwise, there is no way
to actually get the full information, is there? (Other than pg_dump or
manual catalog queries.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Ero | 2020-11-25 08:52:42 | Re: BUG #16732: pg_dump creates broken backups |
| Previous Message | David Turoň | 2020-11-25 07:46:32 | Re: BUG #16743: psql doesn't show whole expression in stored column |