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:39:34
Message-ID: 8343.1133563174@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:
>> That would only affect a standalone backend, however, not normal
>> operation.

> Ah, psql itself is using the same buggy snprintf.c.

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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Jochem van Dieten 2005-12-02 22:41:15 Re: Reducing relation locking overhead
Previous Message Bruce Momjian 2005-12-02 22:38:17 Re: Numeric 508 datatype

Browse pgsql-patches by date

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