Re: Numeric 508 datatype

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Numeric 508 datatype
Date: 2005-12-02 20:15:29
Message-ID: 6605.1133554529@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-patches

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

Responses

Browse pgsql-general by date

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

Browse pgsql-hackers by date

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

Browse pgsql-patches by date

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