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:39:34
Message-ID: 8343.1133563174@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-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

pgsql-hackers by date

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

pgsql-patches by date

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

pgsql-general by date

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

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