From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)postgresql(dot)org, rjuju123(at)gmail(dot)com, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Re: RFC: Allow EXPLAIN to Output Page Fault Information |
Date: | 2025-02-10 22:52:17 |
Message-ID: | CAGECzQTydZ33miLd=KdbfrV17RowRGBwQrS28hZ0i6+YhetYgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 10 Feb 2025 at 14:31, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I think it'll always be a subset of use. It doesn't make sense to use DIO for
> a small databases or untuned databases. Or a system that's deliberately
> overcommmitted.
Thanks, that's useful context.
> But this will also not work with AIO w/ Buffered IO. Which we hope to use much
> more commonly.
To be clear, here you mean worker based AIO right? Because it would
work with io_uring based AIO, right?
> If suddenly I have to reimplement something like this to work with worker
> based IO, it'll certainly take longer to get to AIO.
I totally understand. But in my opinion it would be completely fine to
decide that these new IO stats are simply not available for worker
based IO. Just like they're not available for Windows either with this
patch.
I think it would be a shame to make perfect be the enemy of good here
(as often seems to happen with PG patches). I'd rather have this
feature for some setups, than for no setups at all.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2025-02-10 22:54:22 | Re: AIO v2.3 |
Previous Message | Thomas Munro | 2025-02-10 22:48:38 | Re: AIO v2.3 |