Re: BUG #16743: psql doesn't show whole expression in stored column
От | Peter Eisentraut |
---|---|
Тема | Re: BUG #16743: psql doesn't show whole expression in stored column |
Дата | |
Msg-id | 7a1faa2c-d4d1-67fd-03fe-29ef7e240301@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: BUG #16743: psql doesn't show whole expression in stored column (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #16743: psql doesn't show whole expression in stored column
Re: BUG #16743: psql doesn't show whole expression in stored column |
Список | pgsql-bugs |
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.)
В списке pgsql-bugs по дате отправления: