Re: RFC: Allow EXPLAIN to Output Page Fault Information
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>,
torikoshia <torikoshia@oss.nttdata.com>, pgsql-hackers@postgresql.org,
rjuju123@gmail.com, Bruce Momjian <bruce@momjian.us>
Date: 2025-02-09T18:05:42Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Avoid leaking system path from pg_available_extensions
- db5ed03217b9 19 (unreleased) cited
-
Enable BUFFERS with EXPLAIN ANALYZE by default
- c2a4078ebad7 18.0 cited
Andres Freund <andres@anarazel.de> writes: > I'm somewhat against this patch, as it's fairly fundamentally incompatible > with AIO. There's no real way to get information in this manner if the IO > isn't executed synchronously in process context... Even without looking ahead to AIO, there's bgwriter, walwriter, and checkpointer processes that all take I/O load away from foreground processes. I don't really believe that this will produce useful numbers. regards, tom lane