Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1thcdo-004oRi-8F for pgsql-hackers@arkaria.postgresql.org; Mon, 10 Feb 2025 22:52:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1thcdm-005HjO-D6 for pgsql-hackers@arkaria.postgresql.org; Mon, 10 Feb 2025 22:52:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1thcdm-005HjF-0r for pgsql-hackers@lists.postgresql.org; Mon, 10 Feb 2025 22:52:34 +0000 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1thcdj-0006uh-0b for pgsql-hackers@postgresql.org; Mon, 10 Feb 2025 22:52:32 +0000 Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-308f53aef4fso8589001fa.0 for ; Mon, 10 Feb 2025 14:52:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeltef.nl; s=google; t=1739227949; x=1739832749; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pMj7p5AeXXahhFp8elRNLReI864GUOUt3S7SmvhwOwA=; b=h4Bfk3MKhbCT2+L5tLbWyHaxNVzsqIPzRn7QMd9hr8AUvKlbnR5hTPrJYQsAcDMLD0 61gZ91ymqoI/mrcPpIsdPkw6ZBdxouY9znD9GnBZpdOOWSpNNMq9fKjYRFgkB+eoIq8i 1qEHhy1Yb6Ps/Ci/3AkCRlePR9tlHzCtq1JEg6COIwcWTqX+evtVlU2MbO8emzhuvbZo PSchJOvT1xylFwhpbIU2sdf2fxj1jNSEAwQ9le3DHK7dS35CFF8SkWbGlaTWYVXemyLW kuCcIXiBVdd2Zg8iqI/CqO/vwc+Vo/UrTBkSSV0dE2tEbB3yXcXksazKyk/xRNoKN4kw 98iA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739227949; x=1739832749; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pMj7p5AeXXahhFp8elRNLReI864GUOUt3S7SmvhwOwA=; b=gOzHTQJfq5lgREmLfhZUfAU67giOae9nguA8cIypVNqHyvtqMC1595ccSI1rKQI0+C y3VYG0IITBg1dpH0il6DLrQuCKqCaGetbFqWaYMCRvPg9nlrvMsRAlkOmKazfVvupdTV GzlSBUJ1EsOf6P+k+iauOcbg11/LXR2DbRihxeSyv/6rE4TAXUuF2jHa3XPs8hzi7/W3 bh5hqjobNyJrdYodphWGR9xtRqZnTOo1rW5v1HLg+17kU5CqJ5oFs6utNLvtjAZLubeb WXnyW/SBN/lMznDZS7zjCnHPt5f+JKEP4Tid/3LoqLt1+8k2srZEJLl/eCP9mHuTHeGQ xZGw== X-Forwarded-Encrypted: i=1; AJvYcCXMrUIDTbQVc3C7y2VbiOLZC+LAUk80wPy9Yjv0ZprC8ocOKdSJNQJKCtlQWZ3Yyg8Zrs/ixnJZocQSh7dV@postgresql.org X-Gm-Message-State: AOJu0YzpWzLl/19MEeMz5WB3tQaKsbQTPeccvXkzh1IpDKbgvWUV6LVq GVYT7d8iPxbOTZNSOkMNT6P/xVghKYDyLCjThc7spFTG9YMzVR1Lh3i3/x9uPDy+jCXrokNoNT2 TBz/aEojHmRI6bzbfa1NthuDvAjYfZJrFYP+qaQ== X-Gm-Gg: ASbGncvZAJILdhIo7YZ04F7I4juD2Fv5tG0KmGsiuiGPxeShElNTT2qvmiKIdXCYKqV uwfljEopaoc2MtJoP1lqGBuMKsneNDtDi+zzeIynKDG2EIOztdY49dIe2IaIuh2gKkv4IJd/5aw == X-Google-Smtp-Source: AGHT+IFcQaFlpcL3J1eKZie5j5aPbKVu1S0Qkvz7Mzf6Y8wxkldtx9VsO+ovh1qVps/isXovceewPJfrFrQ3tbtBfVY= X-Received: by 2002:a2e:b8c4:0:b0:308:f53a:ed41 with SMTP id 38308e7fff4ca-308f53af1c1mr14793301fa.32.1739227948292; Mon, 10 Feb 2025 14:52:28 -0800 (PST) MIME-Version: 1.0 References: <1f22794321b745549d54359d343e37b8@oss.nttdata.com> <2c9d6eaf26df17bec13bb03bf1e9bcbb@oss.nttdata.com> <2035079.1739124342@sss.pgh.pa.us> In-Reply-To: From: Jelte Fennema-Nio Date: Mon, 10 Feb 2025 23:52:17 +0100 X-Gm-Features: AWEUYZka7cnYjisC9diad1Knd_VixN6_kGVIerfNi08gFAGp89wfCtXZjEXddz8 Message-ID: Subject: Re: RFC: Allow EXPLAIN to Output Page Fault Information To: Andres Freund Cc: Tom Lane , torikoshia , pgsql-hackers@postgresql.org, rjuju123@gmail.com, Bruce Momjian Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 10 Feb 2025 at 14:31, Andres Freund 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.