News for hackers. Stuff that matters.
Re:The dangers of streaming across versions of glibc: A caut... by rurban on Tuesday January 08, 2019 @06:15PM (#18860749)
That's done via

    unicode/uchar.h:
    #define U_UNICODE_VERSION "9.0"
in icu. pcre2 has PCRE2_CONFIG_UNICODE_VERSION 10 fribidi has FRIBIDI_UNICODE_VERSION "6.2.0"

libc's need something similar. In safelibc I do have nothing so far, but I'm at 11.0

Re:The dangers of streaming across versions of glibc: A caut... by cbsmith on Wednesday January 09, 2019 @02:18PM (#18867845)
Right... so properly detecting when U_UNICODE_VERSION in the replication target differs from U_UNICODE_VERSION in the source, and adjusting for it is what's needed. PostgreSQL wasn't doing this in 2014.
Re:The dangers of streaming across versions of glibc: A caut... by rurban on Thursday January 10, 2019 @06:12AM (#18873038)
Exactly. I'm just not happy with the types of these defines. Only major updates need to be tracked, so the PCRE format seems to be the best. But all others are using strings, not an integer.