ts_parse reports different between MacOS, FreeBSD/Linux

From: "Mark Felder" <feld(at)FreeBSD(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: ts_parse reports different between MacOS, FreeBSD/Linux
Date: 2020-12-22 18:15:39
Message-ID: 543023b3-7c17-4ed5-81d5-c6092ea98919@www.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

We have an application whose test suite fails on MacOS when running the search tests on unicode characters.

I've narrowed it down to the following:

macos=# select * from ts_parse('default','天');
tokid | token
-------+-------
12 | 天
(1 row)

freebsd=# select * from ts_parse('default','天');
tokid | token
-------+-------
2 | 天
(1 row)

This has been bugging me for a while, but it's a test our devs using MacOS just ignores for now as we know it passes our CI/CD pipeline on FreeBSD/Linux. It seems if anyone is shipping an app on MacOS and bundling Postgres they're going to have a bad time with searching.

Please let me know if there's anything I can do to help. Will gladly test patches.

Thanks,

--
Mark Felder
ports-secteam & portmgr alumni
feld(at)FreeBSD(dot)org

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-12-22 18:15:59 Re: Missing rows after migrating from postgres 11 to 12 with logical replication
Previous Message Joel Jacobson 2020-12-22 17:44:57 Re: Avoid excessive inlining?