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 22:49:22
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:
> 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

pgsql-hackers by date

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

pgsql-patches by date

Next:From: Tom LaneDate: 2005-12-02 23:38:01
Subject: Re: Numeric 508 datatype
Previous:From: Bruce MomjianDate: 2005-12-02 22:41:34
Subject: Re: Numeric 508 datatype

pgsql-general by date

Next:From: Tom LaneDate: 2005-12-02 23:06:25
Subject: Re: default_index_tablespace?
Previous:From: Jim C. NasbyDate: 2005-12-02 22:42:49
Subject: Re: default_index_tablespace?

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