From: Tom Lane <tgl@sss.pgh.pa.us>
To: turon.david@seznam.cz
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16743: psql doesn't show whole expression in stored column
In-reply-to: <16743-7b1bacc4af76e7ad@postgresql.org>
References: <16743-7b1bacc4af76e7ad@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 24 Nov 2020 14:17:09 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <286181.1606232817.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 24 Nov 2020 10:46:57 -0500
Message-ID: <286182.1606232817@sss.pgh.pa.us>
Precedence: bulk

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_exp=
r(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.

			regards, tom lane