Re: [PATCH] Fix EINTR retry condition in pg_flush_data sync_file_range path.
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: DaeMyung Kang <charsyam@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2026-04-30T02:48:13Z
Lists: pgsql-hackers
On Thu, Apr 30, 2026 at 12:18:11AM +0900, DaeMyung Kang wrote: > While auditing src/backend/storage/file, I spotted a small but > unambiguous bug in pg_flush_data()'s sync_file_range() retry path. > Details below in the commit message; the fix is a one-token change. Ohh, nice catch. This happens to be wrong since 0d369ac65004. -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix errno check based on EINTR in pg_flush_data()
- 3b35c10a4d50 16.14 landed
- 5499be3325d8 17.10 landed
- 6cb307251c5c 18.4 landed
- 5941e7f09223 19 (unreleased) landed