Request a Demo
Home   >   mailing lists

Re: [Bug Report + Patch] File descriptor leak when io_method=io_uring - Mailing list pgsql-hackers

From Lucas DRAESCHER
Subject Re: [Bug Report + Patch] File descriptor leak when io_method=io_uring
Date
Msg-id PFlQhqaAtrdF4rJvytflIJ7SVtFmeEhF14OaL3bpGotMDnsJE6ht32yyMEYJTYrVp5iFXwOVvQMbgMG9zqkmocmNRAIKgm4NCrJ0gJxWoEg=@draescher.fr
Whole thread
In response to Re: [Bug Report + Patch] File descriptor leak when io_method=io_uring  (Laetitia Avrot <laetitia.avrot@gmail.com>)
List pgsql-hackers
Tree view 
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.

pgsql-hackers by date:

Previous
From: Ewan Young
Date:
Subject: btree_gist: Fix NaN handling in float4 and float8 opclasses
Next
From: Ajin Cherian
Date:
Subject: Re: [PATCH] Preserve replication origin OIDs in pg_upgrade