Re: BUG #3394: Partial search not working
От | Douglas Toltzman |
---|---|
Тема | Re: BUG #3394: Partial search not working |
Дата | |
Msg-id | B856332B-BA5B-403B-BF43-330C1724EBB4@oakstreetsoftware.com обсуждение исходный текст |
Ответ на | Re: BUG #3394: Partial search not working ("Murali Doss" <Murali.Doss@mphasis.com>) |
Ответы |
Re: BUG #3394: Partial search not working
|
Список | pgsql-bugs |
AFAIK, you will need to recreate the database. See "CREATE DATABASE" command for details, but something like "CREATE DATABASE FOO WITH ENCODING 'SQL_ASCII'" should do it... if my memory serves me. Of course, you'll need to dump and reload your data. On Jun 19, 2007, at 8:51 AM, Murali Doss wrote: > Hi Zdenek, > > Thanks for your effort. > > Database encoding for Solaris OS is SQL_ASCII but it's UTF8 in > Linux OS. > How to change the database encoding to sql_ascii for linux OS? > > Regards > Murali Doss T.S. > > > > -----Original Message----- > From: Zdenek.Kotala@Sun.COM [mailto:Zdenek.Kotala@Sun.COM] > Sent: Tuesday, June 19, 2007 5:31 PM > To: Murali Doss > Cc: Michael Fuhr; Heikki Linnakangas; pgsql-bugs@postgresql.org > Subject: Re: [BUGS] BUG #3394: Partial search not working > > Murali Doss wrote: >> Hi Michael, >> >> Same database dump is there Solaris, Windows and Linux and the >> partial >> search query is displaying the expected results in Solaris and >> Windows >> OS but the query returning 0 row in Linux OS. >> >> SELECT * FROM tablename WHERE colname BETWEEN 'B' AND 'B~'; >> >> >> Any query to find the local settings and encoding. >> > > Try > > SELECT name, setting FROM pg_settings WHERE name LIKE 'lc_%'; > > The psql -l command shows you database encoding. Client and server > encoding is possible get by the following commands: > > SHOW client_encoding and SHOW server_encoding > > > Zdenek > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq Douglas Toltzman doug@oakstreetsoftware.com (910) 526-5938
В списке pgsql-bugs по дате отправления: