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:29:59
Message-ID: 200512022229.jB2MTxa01974@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-patches

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> Uh, how is control getting to snprintf? I don't see that used either
> >> in numeric.c or in printtup.c.
>
> > I am seeing it in the standalone backend here:
>
> > debugtup (slot=0x856e0b0, self=0x84306d0) at printtup.c:548
> > 548 printatt((unsigned) i + 1, typeinfo->attrs[i], value);
>
> That would only affect a standalone backend, however, not normal
> operation.

Ah, psql itself is using the same buggy snprintf.c. That would explain
the long dash line, but short digits.

--
Bruce Momjian | http://candle.pha.pa.us
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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2005-12-02 22:38:17 Re: Numeric 508 datatype
Previous Message Tom Lane 2005-12-02 22:26:58 Re: Numeric 508 datatype

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2005-12-02 22:34:57 Re: Reducing relation locking overhead
Previous Message Tom Lane 2005-12-02 22:26:58 Re: Numeric 508 datatype

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-12-02 22:38:17 Re: Numeric 508 datatype
Previous Message Tom Lane 2005-12-02 22:26:58 Re: Numeric 508 datatype