On 7 April 2011 08:10, Thom Brown <t...@linux.com> wrote: > On 7 April 2011 07:37, Tom Lane <t...@sss.pgh.pa.us> wrote: >> Thom Brown <t...@linux.com> writes: >>> On 6 April 2011 05:44, Tom Lane <t...@sss.pgh.pa.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.
Nevermind. This was caused by "Add casts from int4 and int8 to numeric.". -- Thom Brown Twitter: @darkixion IRC (freenode): dark_ixion Registered Linux user: #516935 EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
