Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Actually, no.  If I cut'n paste the number from psql to
> cat > foo
> <shift> <insert>
> then only 4096 chars are copied.  (Amusingly, I can't add a newline to
> ^D and close the file.  I must delete one char to do that.)

Hmm, cut buffer limitation in X or someplace?  I definitely get the
right number of characters into the file written with \g, and what looks
like a reasonable number of screensful of plain psql output.  If Bruce
is seeing the right number of dashes and the wrong number of data
characters in his \g output then *something* is pretty weird there.

			regards, tom lane

In response to

• Re: Numeric 508 datatype at 2005-12-02 20:12:00 from Alvaro Herrera

Responses

• Re: Numeric 508 datatype at 2005-12-02 20:26:34 from Alvaro Herrera

pgsql-hackers by date

Next:	From: Greg Stark	Date: 2005-12-02 20:25:58
	Subject: Re: Reducing relation locking overhead
Previous:	From: Bruce Momjian	Date: 2005-12-02 20:14:31
	Subject: Re: Numeric 508 datatype

pgsql-patches by date

Next:	From: Alvaro Herrera	Date: 2005-12-02 20:26:34
	Subject: Re: Numeric 508 datatype
Previous:	From: Bruce Momjian	Date: 2005-12-02 20:14:31
	Subject: Re: Numeric 508 datatype

pgsql-general by date

Next:	From: Harakiri	Date: 2005-12-02 20:26:03
	Subject: Re: deadlock detected - when multiple threads try to update one table
Previous:	From: Bruce Momjian	Date: 2005-12-02 20:14:31
	Subject: Re: Numeric 508 datatype