From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Numeric 508 datatype |
Date: | 2005-12-02 21:10:22 |
Message-ID: | 7170.1133557822@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> If that gives the right answer then the NUMERIC code is off the hook,
>> and what you've got is a strange limitation on output column length.
> test=> select length((pow(10::numeric, 131071))::text);
> length
> --------
> 131089
> (1 row)
> Looks good. From psql I just tried:
> SELECT repeat('x', 4000);
> and got 4k x's, and SELECT repeat('x', 8000) returns 8k x's, so that works.
Curiouser and curiouser. How about if you repeat 4k or 8k '1's? If the
behavior is different for letters and digits then I'd look at the column
justification logic in psql's printing code.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-02 21:19:20 | Re: Numeric 508 datatype |
Previous Message | Tom Lane | 2005-12-02 21:06:31 | Re: createuser ignores stdin in 8.1.0? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-02 21:19:20 | Re: Numeric 508 datatype |
Previous Message | Bruce Momjian | 2005-12-02 21:05:28 | Re: Numeric 508 datatype |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-02 21:19:20 | Re: Numeric 508 datatype |
Previous Message | Bruce Momjian | 2005-12-02 21:05:28 | Re: Numeric 508 datatype |