Re: [Bug Report + Patch] File descriptor leak when io_method=io_uring

From: Lucas DRAESCHER <git(at)draescher(dot)fr>
To: Laetitia Avrot <laetitia(dot)avrot(at)gmail(dot)com>, "tanswis42(at)gmail(dot)com" <tanswis42(at)gmail(dot)com>
Cc: cca5507 <cca5507(at)qq(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [Bug Report + Patch] File descriptor leak when io_method=io_uring
Date: 2026-06-17 09:09:46
Message-ID: PFlQhqaAtrdF4rJvytflIJ7SVtFmeEhF14OaL3bpGotMDnsJE6ht32yyMEYJTYrVp5iFXwOVvQMbgMG9zqkmocmNRAIKgm4NCrJ0gJxWoEg=@draescher.fr
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ilmar, Lætitia,

Thank you for taking the time to review my patch!

> On the v1 vs v2 design question: I favour v2.
> The Table AM precedent suggests PostgreSQL prefers
> clean interface boundaries even with a single
> implementor, and Andres Freund has been explicit
> about this in the past.

Thanks for the feedback, I'm happy for v2 to be the
design we settle on.

Thanks again to both of you for your help.

Lucas.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ajin Cherian 2026-06-17 09:19:19 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade
Previous Message Ewan Young 2026-06-17 08:39:39 btree_gist: Fix NaN handling in float4 and float8 opclasses