Received: from dcave.digsys.bg (root@dcave.digsys.bg [192.92.129.5]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA93156 for ; Wed, 9 Jun 1999 09:54:42 -0400 (EDT) (envelope-from daniel@dcave.digsys.bg) Received: from dcave.digsys.bg (daniel@localhost.digsys.bg [127.0.0.1]) by dcave.digsys.bg (8.9.0/8.9.0) with ESMTP id QAA19490; Wed, 9 Jun 1999 16:53:20 +0300 (EEST) Message-Id: <199906091353.QAA19490@dcave.digsys.bg> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Momjian cc: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem In-reply-to: Your message of "Wed, 09 Jun 1999 16:15:58 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Jun 1999 16:53:19 +0300 From: Daniel Kalchev Further to my cyrillic charset (--enable-locale) introduced woes, I would like to add, that when recompiling Postgres 6.5 without --enable-locale now the query runs reasonably fast and explain gives: Index Scan using w_k_words_i on words (cost=1112.13 rows=1 width=12) instead of Index Scan using w_k_words_i on words (cost=3335.38 rows=1 width=12) The problem as it seems is that the restrictions to use indexes when locale is enabled are not consistently applied - explain shows that indices will be used, and the behavior with indexes and without indexes is different (with indexes it's noticeably slower :-) so indexes are apparently being used... Apparently (for my current tests at least) the Bulgarian cyrillic (windows-1251) is handled reasonably well without locale support - untill now ~* didn't work anyway. Daniel Kalchev