Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-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

pgsql-hackers by date

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

pgsql-patches by date

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

pgsql-general by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group