From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Philip Rhoades <phil(at)pricom(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Displaying a wide column with psql |
Date: | 2014-09-02 04:11:19 |
Message-ID: | 27713.1409631079@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:
>> On 09/01/2014 08:05 PM, Philip Rhoades wrote:
>>> I have a table with a field that has up to 1,000 chars in it, when I
>>> look at it with psql it only displays about 200 chars with a "…"
>>> on the end of the string.
> I presume what you are seeing is effectively: "this is some really long
> con..." where the content is truncated and replaced a final trailing three
> periods (possible actual ellipses)
> Also, are you sure you are not sending this to a pager?
Yeah, it's pretty hard to credit this happening in a vanilla
configuration. I suspect that Philip either has some nondefault
\pset option selected, or is sending his output to a pager program
that thinks that the ellipsis is a good idea.
For starters, try "\pset pager off" and see if you still see the
ellipsis after that. If so, we'll need some more info about exactly
which PG version you're using and with what \pset options. If you
have a ~/.psqlrc file, that's probably what's setting nondefault options.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-09-02 04:40:59 | Re: copymanager question |
Previous Message | David G Johnston | 2014-09-02 03:59:28 | Re: Displaying a wide column with psql |