Possible bug in Postgres String comparison routines

From: Peter Breton <pbreton(at)MIT(dot)EDU>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Possible bug in Postgres String comparison routines
Date: 2001-10-24 16:15:06
Message-ID: 3BD6E90A.7060501@mit.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On my Postgres system ( PostgreSQL 7.1.2 on i686-pc-linux-gnu, compiled
by GCC 2.96), I get the following odd behavior in string compares:

# Works -- e (ASCII code 101) is after comma (ASCII code 44)
select current_time where 'e' > ',';

# Works -- adding a k to the front of both strings
select current_time where 'ke' > 'k,';

# Works -- add some trailing characters. Note that since 'ke' > 'k,'
# we should be able to add whatever trailing characters we want
# and still get the same result
select current_time where 'ken' > 'k, ';

# Does not work!!!
select current_time where 'kens' > 'k, P';
# Also does not work
select current_time where 'ens' > ', P';

For "Works", I mean returns a result (the where expression evaluated
true); "Does not work" means no result was returned.

Is there something that I'm not understanding here, or is this a bug?

Peter

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-10-24 17:02:46 Re: Bug #490: Can't compile PostgreSQL 7.1.3 with Solaris 2.6
Previous Message Arguile 2001-10-24 15:38:38 New default ignored by pre-exising insert rulesets.