Re: Numeric 508 datatype - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: Numeric 508 datatype
Date
Msg-id 200512022223.jB2MNrH01134@candle.pha.pa.us
Whole thread Raw
In response to Re: Numeric 508 datatype  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Numeric 508 datatype  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I found the cause.  I traced into printf then realized I was not in libc
> > but port/snprintf.c, and I see 4096 defined for those buffers.
>
> 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);
    (gdb) s
    printatt (attributeId=1, attributeP=0x856efa4, value=0x857201c "1", '0' <repeats 199 times>...) at printtup.c:480
    480             printf("\t%2d: %s%s%s%s\t(typeid = %u, len = %d, typmod = %d, byval = %c)\n",

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

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Numeric 508 datatype
Next
From: Tom Lane
Date:
Subject: Re: Numeric 508 datatype