Skip site navigation (1) Skip section navigation (2)

Re: Numeric 508 datatype

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(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:41:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackerspgsql-patches
Tom Lane wrote:
> 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.

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

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2005-12-02 22:45:05
Subject: Re: Optional postgres database not so optional in 8.1
Previous:From: Jochem van DietenDate: 2005-12-02 22:41:15
Subject: Re: Reducing relation locking overhead

pgsql-patches by date

Next:From: Tom LaneDate: 2005-12-02 22:49:22
Subject: Re: Numeric 508 datatype
Previous:From: Tom LaneDate: 2005-12-02 22:39:34
Subject: Re: Numeric 508 datatype

pgsql-general by date

Next:From: Jim C. NasbyDate: 2005-12-02 22:42:49
Subject: Re: default_index_tablespace?
Previous:From: Tom LaneDate: 2005-12-02 22:39:34
Subject: Re: Numeric 508 datatype

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