Re: Numeric 508 datatype

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: Michael Fuhr <mike(at)fuhr(dot)org>, 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 23:38:01
Message-ID: 8915.1133566681@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:
> Yep, I am digging through snprintf.c now to try find a solution.

The cleanest solution is probably to fix things so that dopr_outch is
aware of whether it's working for sprintf or fprintf, and can dump the
buffer directly to the file when it gets full in the fprintf case.
Its existing API would need to be changed a bit ... maybe pass it a
struct containing what it needs, instead of having all the layers of
code know what to pass.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2005-12-02 23:46:16 Re: 8.1, OID's and plpgsql
Previous Message Jim C. Nasby 2005-12-02 23:37:28 Re: default_index_tablespace?

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2005-12-02 23:44:20 strange behavior (corruption?) of large production database
Previous Message Tom Lane 2005-12-02 23:32:57 Re: Reducing relation locking overhead

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-12-03 00:37:49 Re: Reduce NUMERIC size by 2 bytes, reduce max length to 508 digits
Previous Message Tom Lane 2005-12-02 22:49:22 Re: Numeric 508 datatype