Bruce Momjian wrote:
> > If you run the query that fails in a standalone backend, do you get
> > something like "(typeid = 1700, len = -1, typmod = -1, byval = f)"
> > at the end of the line, or is that part truncated too?
> 
> 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.  I will
> work on a patch to make it dynamic.  At the time I think there was
> thought that 4096 was as large as it ever needed to be, but obviously
> this was wrong. I think Win32 would see the same failure because it used
> port/snprintf.c too.

My Win32 8.1 platform is fine so Win32 must not use port/snprintf.c.

-- 
  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

• Re: Numeric 508 datatype at 2005-12-02 22:11:13 from Bruce Momjian

pgsql-hackers by date

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

pgsql-patches by date

Next:	From: Tom Lane	Date: 2005-12-02 22:39:34
	Subject: Re: Numeric 508 datatype
Previous:	From: Bruce Momjian	Date: 2005-12-02 22:29:59
	Subject: Re: Numeric 508 datatype

pgsql-general by date

Next:	From: Tom Lane	Date: 2005-12-02 22:39:34
	Subject: Re: Numeric 508 datatype
Previous:	From: Bruce Momjian	Date: 2005-12-02 22:29:59
	Subject: Re: Numeric 508 datatype