Horton
Menu

Re: GNU/Hurd portability patches

Samuel Thibault <samuel.thibault@gnu.org>

View thread
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Michael Banck <mbanck@gmx.net>
Cc: Thomas Munro <thomas.munro@gmail.com>, Alexander Lakhin <exclusion@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers@lists.postgresql.org
Date: 2026-02-05T08:35:40Z
Lists: pgsql-hackers 
Hello,

Michael Banck, le jeu. 05 févr. 2026 09:27:37 +0100, a ecrit:
> With the glibc patch from [2] applied, I have been running the above SQL
> for 5 million iterations without a hang just now. So those semi-frequent
> hangs on fruitcrow should be fixed now, yay!

Yay!

Thanks for taking the time to get the backtrace that explained it all :)

> > * I see special code paths for threads that were in (its notion of)
> > critical sections, which must be rare, but it looks like that just
> > leave it pending which seems reasonable

That's what was missing in cancellation checks. A very small window, but
still there so happened of course :)

Take the two most tricky things in Unix (signals and thread
cancellation) ; that was deemed to pose very tricky problems :)

Samuel

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add minimal sleep to stats isolation test functions.

  2. Include pg_test_timing's full output in the TAP test log.

  3. Make sure IOV_MAX is defined.

  4. Make safeguard against incorrect flags for fsync more portable.