Skip site navigation (1) Skip section navigation (2)

Re: BUG #6760: make check fails on strings SQL T581 regex test

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jez(dot)wain(at)bull(dot)net
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6760: make check fails on strings SQL T581 regex test
Date: 2012-07-25 17:10:15
Message-ID: 29371.1343236215@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
jez(dot)wain(at)bull(dot)net writes:
> ***************
> *** 347,354 ****
>    three |          f1          |       exp_ln_f1       
>   -------+----------------------+-----------------------
>          |               1004.3 |                1004.3
> !        | 1.2345678901234e+200 | 1.23456789012338e+200
> !        | 1.2345678901234e-200 | 1.23456789012339e-200
>   (3 rows)
  
>   -- cube root
> --- 347,354 ----
>    three |          f1          |       exp_ln_f1       
>   -------+----------------------+-----------------------
>          |               1004.3 |                1004.3
> !        | 1.2345678901234e+200 | 1.23456789012337e+200
> !        | 1.2345678901234e-200 |  1.2345678901234e-200
>   (3 rows)

This doesn't seem terribly surprising as a platform-specific difference.

>   -- T581 regular expression substring (with SQL99's bizarre regexp syntax)
>   SELECT SUBSTRING('abcdefg' FROM 'a#"(b_d)#"%' FOR '#') AS "bcd";
> ! ERROR:  invalid regular expression: parentheses () not balanced
> ! CONTEXT:  SQL function "substring" statement 1

This however isn't too good.  It suggests a platform-specific issue in
the regex library, but hard to say what.  Can you dig a little deeper,
maybe get a stack trace back from the call to errfinish()?  Does
compiling with -O0 change the behavior?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2012-07-25 18:34:46
Subject: Re: BUG #6759: configure script fails to detect xlc compiler version
Previous:From: Tom LaneDate: 2012-07-25 17:05:37
Subject: Re: BUG #6758: ./configure script sets HAVE_WCSTOMBS_L 1

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group