case sensitive/insensitive confusion

From: Christoph Haller <ch(at)rodos(dot)fzk(dot)de>
To: pgsql-sql(at)postgresql(dot)org
Subject: case sensitive/insensitive confusion
Date: 2005-02-01 09:50:06
Message-ID: 41FF50CE.76CEB361@rodos.fzk.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

I am seeing different ORDER BY results
on a character column on different machines.
I have (1)
ResyDBE=# select version();
version
------------------------------------------------------------------------
PostgreSQL 7.4.5 on hppa-hp-hpux10.20, compiled by GCC gcc (GCC) 3.3.1

ResyDBE=# \l ResyDBE
List of databases
Name | Owner | Encoding
-----------+-------+-----------
ResyDBE | rodos | SQL_ASCII

ResyDBE=# select parameter_name from parameter_define where
parameter_name ilike 'c%' order by 1 limit 8;
parameter_name
----------------
CAENAM
CAENAM
CAENAM
CBERRY
CBERRY
CCCTOG
CCCTOG
CCCTOG

and (2)
ResyDBE=# select version();

version
-------------------------------------------------------------------------------------
PostgreSQL 7.4.5 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.1
(SuSE Linux)

ResyDBE=# \l
List of databases
Name | Owner | Encoding
-----------+-------+-----------
ResyDBE | rodos | SQL_ASCII

ResyDBE=# select parameter_name from parameter_define where
parameter_name ilike 'c%' order by 1 limit 8;
parameter_name
----------------
c12a
c12b
c12c
c1a
CAENAM
CAENAM
CAENAM
CAENAM

It seems to me under hpux the sort is done case sensitive,
as would one expect on SQL_ASCII encoding, whereas
under linux a case insensitive sort is done.
I'd like to see the hpux behaviour under linux too.
Has anybody seen something like this?
TIA

Regards, Christoph

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Peter Eisentraut 2005-02-01 10:14:00 Re: case sensitive/insensitive confusion
Previous Message PFC 2005-02-01 09:16:47 Re: [SQL] OFFSET impact on Performance???