Re: [PATCH] Fix EINTR retry condition in pg_flush_data sync_file_range path.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: DaeMyung Kang <charsyam(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Fix EINTR retry condition in pg_flush_data sync_file_range path.
Date: 2026-04-30 02:48:13
Message-ID: afLC7ZCsHDRrQCt8@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2026-04-30 03:08:46 Re: Fix HAVING-to-WHERE pushdown with nondeterministic collations
Previous Message Michael Paquier 2026-04-30 02:33:35 Re: Fix the error hint message and test for reset_shared with unknown stats type