Re: create index regression fail
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jaime Casanova <jaime@2ndquadrant.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-01-12T18:59:49Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Improve planner's handling of duplicated index column expressions.
- e2c2c2e8b1df 9.2.0 cited
Jaime Casanova <jaime@2ndquadrant.com> writes: > the query where the regression fails is: > SELECT count(*) FROM dupindexcols > WHERE f1 > 'LX' and id < 1000 and f1 ~<~ 'YX'; > my first theory was that it was because some locale because mine is > es_EC.UTF-8 but the content of the table doesn't justify that, [ experiments... ] Looks like you're wrong about that. In ec_EC locale on my machine, the test accepts these rows that are not accepted in C locale: 223 | LLKAAA 738 | LLEAAA I'll change the lower bound to 'MA' and see if that's any more portable. regards, tom lane