On 2020-11-24 16:46, Tom Lane wrote: > PG Bug reporting form <noreply@postgresql.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.)
Either that or we have to make it clear that the output is truncated: otherwise it can be mighty confusing.