Received: from kodu.home.ee (isdn-54.uninet.ee [194.204.0.118]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA42809 for ; Wed, 9 Jun 1999 14:57:54 -0400 (EDT) (envelope-from hannu@trust.ee) Received: from trust.ee (hannu@localhost [127.0.0.1]) by kodu.home.ee (8.8.7/8.8.7) with ESMTP id WAA00583; Wed, 9 Jun 1999 22:04:00 +0300 Sender: hannu@kodu.home.ee Message-ID: <375EBAA0.D5DE4B2E@trust.ee> Date: Wed, 09 Jun 1999 22:04:00 +0300 From: Hannu Krosing Organization: Trust-O-Matic =?iso-8859-1?Q?O=DC?= X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.2.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Oleg Bartunov CC: ZEUGSWETTER Andreas IZ5 , "'hackers@postgresql.org'" Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Oleg Bartunov wrote: > > > Thanks for explanations. It would be great if I could specify for specific > columns if it needs locale. For now I have to pay decreasing in speed > just to enable locale for the only column of one database !!! > I always dream to be able to specify on fly 'SET LOCALE to ON|OFF' > It's a bit separate problem, but probably more easy to implement. Actually the locale should be part of field definition (like length and precision currently are) with default of ascii. And also it may be probably safest to maintain our own locale defs (as Oracle currently does)so that things don't break if somebody changes the system ones. ------------- Hannu