From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Partial index slower than regular index |
Date: | 2011-04-07 07:10:14 |
Message-ID: | BANLkTinjknsFSSdDgVqmgoZV-EnLRP3jOQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 7 April 2011 07:37, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thom Brown <thom(at)linux(dot)com> writes:
>> On 6 April 2011 05:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> It looks like the index predicate expression isn't getting the right
>>> collation assigned, so predtest.c decides the query doesn't imply the
>>> index's predicate. Too tired to look into exactly why right now, but
>>> it's clearly bound up in all the recent collation changes.
>
>> Testing it again with very explicit collations, it still has issues:
>
> Yeah, any sort of collation-sensitive operator in an index WHERE clause
> was just plain broken. Fixed now.
Thanks Tom.
You said in the commit message that an initdb isn't required, but is
there anything else since 20th March that would cause cluster files to
break compatibility? I'm now getting the following message:
toucan:postgresql thom$ pg_ctl start
server starting
toucan:postgresql thom$ FATAL: database files are incompatible with server
DETAIL: The database cluster was initialized with CATALOG_VERSION_NO
201103201, but the server was compiled with CATALOG_VERSION_NO
201104051.
HINT: It looks like you need to initdb.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-04-07 08:01:58 | Re: Partial index slower than regular index |
Previous Message | Tom Lane | 2011-04-07 06:37:29 | Re: Partial index slower than regular index |