Top all-time · #6681
Daniel Vérité
Personal blog · postgresql.verite.pro/blogdataprogramming
Daniel Vérité writes PostgreSQL Notes, a personal blog at postgresql.verite.pro about data and programming. Since 2018, 12 different Hacker News readers have linked it 14 times, most often “Beware of your next glibc upgrade”. It is still writing: the last post was on 2025-11-05, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
Commenters cite these PostgreSQL posts on glibc upgrades and ICU collations, which cover how libc collation changes can break sort order and require index rebuilds. They serve as the reference for that problem.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
A blog about working with PostgreSQL.
Most-linked posts?
- Beware of your next glibc upgrade4 people · 4 mentions · first linked 2018-08-27
- Static and dynamic pivots in PostgreSQL (2018)2 people · 2 mentions · first linked 2018-06-26
- Isolation Repeatable Read in PostgreSQL versus MySQL2 people · 2 mentions · first linked 2020-02-14
- PostgreSQL Nondeterministic Collations (2019)2 people · 2 mentions · first linked 2019-10-17
What Hacker News says?
The updated variant of this postgresql/glibc warning and story is https://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade.... And glibc is still 2 years behind in its unicode version: they are at 9.0, current is 11.0. musl is at 6.0
Comment linking /blog/2018/08/27/glibc-upgrade.html
on “The dangers of streaming across versions of glibc: A cautionary tale (2014)”Submitted Pipelining in psql (PostgreSQL 18) as a story · 165 points
HN discussionArch package is configured with ICU support, but I think you need to use ICU collations explicitly: https://postgresql.verite.pro/blog/2018/07/25/icu-extension.... SELECT * FROM pg_catalog.pg_collation; As usual with collations, you must be careful and know what you are doing (old collations are also still available, for backwards compatibility)
Comment linking /blog/2018/07/25/icu-extension.html
on “The dangers of streaming across versions of glibc: A cautionary tale (2014)”Submitted PostgreSQL Nondeterministic Collations (2019) as a story · 8 points
HN discussionCorrect. Using ICU collations avoids this problem. Also, with libc collations you have to rebuild indexes after a glibc upgrade: https://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade....
Comment linking /blog/2018/08/27/glibc-upgrade.html
on “The dangers of streaming across versions of glibc: A cautionary tale (2014)”Submitted Beware of your next glibc upgrade as a story · 4 points
HN discussionThis is still an issue : https://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade....
Comment linking /blog/2018/08/27/glibc-upgrade.html
on “The dangers of streaming across versions of glibc: A cautionary tale (2014)”Submitted Transaction isolation repeatable read in PostgreSQL vs. MySQL as a story · 3 points
HN discussionSubmitted Isolation Repeatable Read in PostgreSQL versus MySQL as a story · 3 points
HN discussionSubmitted Static and dynamic pivots in PostgreSQL (2018) as a story · 2 points
HN discussionSubmitted A psql hack for select * except some columns as a story · 1 points
HN discussionSubmitted Nondeterministic Collations in PostgreSQL 12 as a story · 1 points
HN discussionSubmitted OIDs demoted to normal columns: a glance at the past as a story · 1 points
HN discussionSubmitted Static and dynamic pivots as a story · 1 points
HN discussion
