Re: contrib/cube & contrib/seg regression fixes - Mailing list pgsql-patches

From Joe Conway
Subject Re: contrib/cube & contrib/seg regression fixes
Date
Msg-id 3D83F33D.5010806@joeconway.com
Whole thread Raw
In response to contrib/cube & contrib/seg regression fixes  (Joe Conway <mail@joeconway.com>)
Responses Re: contrib/cube & contrib/seg regression fixes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:
> Joe Conway <mail@joeconway.com> writes:
>
>>The attached fixes regression test failures in contrib/cube & contrib/seg.
>>Both had error message wording that changed.
>
> [ scratches head... ]  They both pass for me already, and would fail if
> this patch were to be applied.

The message seems to be coming from bison:

#0  elog (lev=20, fmt=0x82c038c "parse error, unexpected $undefined.,
expecting FLOAT or O_PAREN or O_BRACKET at or before position 1, character
('A', \\101), input: 'ABC'\n") at elog.c:114
#1  0x40019093 in cube_yyerror (msg=0xbfffe300 "parse error, unexpected
$undefined., expecting FLOAT or O_PAREN or O_BRACKET") at cubeparse.y:204
#2  0x40018dab in cube_yyparse (result=0xbfffe8b0) at
/usr/share/bison/bison.simple:799
#3  0x40015a87 in cube_in (str=0x82c02a4 "ABC") at cube.c:102

I'm using bison-1.35. Recommendations, or should I ignore the regression failures?

Joe


pgsql-patches by date:

Previous
From: "Arturo Josè Montes Sinning"
Date:
Subject: Patch to return last tid
Next
From: Tom Lane
Date:
Subject: Re: contrib/cube & contrib/seg regression fixes