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 22:49:22
Message-ID: 8471.1133563762@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:
>> Doh. OK, we gotta fix it then. But what are you going to do when you
>> can't malloc enough memory? You can't ereport in a client environment,
>> and there's no API for printf to report failure.

> Yep, I am digging through snprintf.c now to try find a solution.

Well, there's always the option of going back to plan B, which is not
using printf for strings that might be long. AFAICS it would only be
a convenience for psql, since it's not doing any real conversions,
just inserting the right number of spaces.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-12-02 23:06:25 Re: default_index_tablespace?
Previous Message Jim C. Nasby 2005-12-02 22:42:49 Re: default_index_tablespace?

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2005-12-02 23:01:36 Re: generalizing the planner knobs
Previous Message Simon Riggs 2005-12-02 22:47:35 Spam 508

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-12-02 23:38:01 Re: Numeric 508 datatype
Previous Message Bruce Momjian 2005-12-02 22:41:34 Re: Numeric 508 datatype