public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: Bertrand Drouvot <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: [email protected]
Subject: Re: per backend WAL statistics
Date: Wed, 5 Feb 2025 19:31:13 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <Z6M7/[email protected]>
References: <xibh465r3x7xvpzaozu47fxule3dktvwz4yacce4pjlw76lkjd@fjvm56zbev37>
<Z4k9rb3aTNVSmyq/@ip-10-97-1-34.eu-west-3.compute.internal>
<aj5vdgpbux5e2dbr6gcgd4eu3krjrflljt2neivh2vbkfrlant@2qedfymz7lmh>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<Z6M7/[email protected]>
On Wed, Feb 05, 2025 at 10:22:55AM +0000, Bertrand Drouvot wrote:
> So, wal_buffers_full has been introduced after the WalUsage structure was
> there but I don't see any reason in the emails as to why it's not in the WalUsage
> structure (I might have missed it though).
>
> I think that this proposal makes sense but would need a dedicated thread,
> thoughts?
Using a separate thread for a change like that makes sense to me. I
have to admit that the simplifications in terms of designs for what
we're discussing here makes such a change more valuable. Adding this
information to WalUsage is one thing. Showing it in EXPLAIN is a
second thing. Doing the former simplifies the patch you are proposing
here. We don't necessarily have to do the latter, but I don't see a
reason to not do it, either.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, ../[email protected]/2-signature.asc)
download
view thread (20+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: per backend WAL statistics
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox