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: 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: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackerspgsql-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


pgsql-hackers by date

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

pgsql-patches by date

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

pgsql-general by date

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

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