Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > With today's CVS code (originally noticed with 8.2beta3), on a PC where
> > INT_MAX=0x7FFF=2147483647
>
> > postgres=# select to_char(2147483648,'999,999,999');
> > WARNING: detected write past chunk end in ExprContext 0x845509c
imad <[EMAIL PROTECTED]> writes:
> This is the problematic part in formatting.c, function "dch_time".
> intsiz = strlen(tmtcTzn(tmtc));
>
> if (arg == DCH_TZ)
> strcpy(inout, tmtcTzn(tmtc));
> else
> {
>
This is the problematic part in formatting.c, function "dch_time".
int siz =
strlen(tmtcTzn(tmtc));
if (arg == DCH_TZ)
strcpy(inout, tmtcTzn(tmtc));
Patrick Welche <[EMAIL PROTECTED]> writes:
> With today's CVS code (originally noticed with 8.2beta3), on a PC where
> INT_MAX=0x7FFF=2147483647
> postgres=# select to_char(2147483648,'999,999,999');
> WARNING: detected write past chunk end in ExprContext 0x845509c
> WARNING: detected write
Patrick Welche wrote:
> With today's CVS code (originally noticed with 8.2beta3), on a PC where
> INT_MAX=0x7FFF=2147483647
>
> postgres=# select to_char(1234567890123,'999,999,999,999');
> WARNING: detected write past chunk end in ExprContext 0x845509c
> WARNING: detected write past chunk e
With today's CVS code (originally noticed with 8.2beta3), on a PC where
INT_MAX=0x7FFF=2147483647
postgres=# select version();
version
