Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: write past chunk end in ExprContext / to_char
- From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: write past chunk end in ExprContext / to_char
- Date: Thu, 28 Jun 2007 14:29:12 -0400
Patrick Welche wrote: > With today's CVS code (originally noticed with 8.2beta3), on a PC where > INT_MAX=0x7FFFFFFF=2147483647 > > postgres=# select to_char(1234567890123,'999,999,999,999'); > WARNING: detected write past chunk end in ExprContext 0x845509c > WARNING: detected write past chunk end in ExprContext 0x845509c > to_char > ------------------ > ###,###,###,### > (1 row) Yes, it fails in 7.3, 7.4, 8.0, 8.1, 8.2 and HEAD. Thanks for the report. -- Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC "Executive Executive Summary: The [Windows] Vista Content Protection specification could very well constitute the longest suicide note in history." Peter Guttman, http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt
- References:
- write past chunk end in ExprContext / to_char
- From: Patrick Welche
- write past chunk end in ExprContext / to_char
- Prev by Date: Re: SetBufferCommitInfoNeedsSave and race conditions
- Next by Date: Re: write past chunk end in ExprContext / to_char
- Previous by thread: write past chunk end in ExprContext / to_char
- Next by thread: Re: write past chunk end in ExprContext / to_char
- Indexes: