| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Kliukin <alexk(at)hintbits(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: regex match and special characters |
| Date: | 2018-08-16 13:57:39 |
| Message-ID: | 9646.1534427859@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alex Kliukin <alexk(at)hintbits(dot)com> writes:
> Here is a simple SQL statement that gives different results on PostgreSQL 9.6 and PostgreSQL 10+. The space character at the end of the string is actually U+2006 SIX-PER-EM SPACE (http://www.fileformat.info/info/unicode/char/2006/index.htm)
I think the reason for the discrepancy is that in v10 we fixed the regex
locale support so that it could properly classify code points above U+7FF,
cf
So 10 is giving the right answer (i.e. that \s matches U+2006).
9.x is not, but we're not going to back-patch such a large change.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2018-08-16 14:00:31 | Re: Copy over large data Postgresql 9.5 |
| Previous Message | Adrian Klaver | 2018-08-16 13:57:18 | Re: During promotion, new master tries to archive same segment twice |