On Wed, Sep 17, 2014 at 10:06 AM, Matthew Kelly <mke...@tripadvisor.com> wrote: > Let me double check that assertion before we go too far with it. > > Most of the problems I've seen are across 5 and 6 boundaries. I thought I > had case where it was within a minor release but I can't find it right now. > I'm going to dig. > > That being said the sort order changes whether you statically or dynamically > link (demonstrated on 4+ machines running different linux flavors), so at the > point I have no reason to trust the stability of the sort across any build. > I legitimately question whether strcoll is buggy. Ex. I have cases where for > three strings a, b and c: a > b, but (a || c) < (b || c). That's right > postfixing doesn't hold. It actually calls into question the index scan > optimization that occurs when you do LIKE 'test%' even on a single machine, > but I don't want to bite that off at the moment. > > My mentality has switched to 'don't trust any change until shown otherwise', > so that may have bled into my last email.
Of course, there's also the question of whether ICU would have similar issues. You're assuming that they *don't* whack the collation order around in minor releases, or at least that they do so to some lesser degree than glibc, but is that actually true? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
