public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: Postgres Load Profile
Date: Mon, 3 Nov 2025 21:49:01 -0500
Message-ID: <CANzqJaBpi-VMu9xOj-qksKoLLoggZNTi13ZUu5eea8M5Rc6eow@mail.gmail.com> (raw)
In-Reply-To: <CAN6TVjmH8=dszn3WqSE4MsYEZgCT1gQhufoSnPBn-Omcu9-EkQ@mail.gmail.com>
References: <CAN6TVjmH8=dszn3WqSE4MsYEZgCT1gQhufoSnPBn-Omcu9-EkQ@mail.gmail.com>
On Mon, Nov 3, 2025 at 5:56 PM Sam Stearns <[email protected]> wrote:
> Howdy,
>
> Does Postgres have any tables you can query to find out information such
> as:
>
> - Logical reads
> - Block changes
> - Physical reads
> - Physical writes
> - Read IO requests
> - Write IO requests
> - Read IO (MB)
> - Write IO (MB)
>
>
https://www.postgresql.org/docs/17/monitoring-stats.html
>
> - User calls
> - Parses (SQL)
> - Hard parses (SQL)
> - Executes (SQL)
>
> Probably not unless you want to set log_statement=all and then
parse log_directory/log_filename.
>
> - Transactions per second
>
> Does TPS make any sense beyond when DBMS is running a "strict monoculture"
application like OLTP with *zero* report generation? Because a five hour
SELECT that joins 42 tables in addition to 37 hairy subqueries is just as
much a transaction as is a 5 microsecond SELECT of one customer's records
using a hash index, and an equally fast INSERT of three records.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (5+ 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]
Subject: Re: Postgres Load Profile
In-Reply-To: <CANzqJaBpi-VMu9xOj-qksKoLLoggZNTi13ZUu5eea8M5Rc6eow@mail.gmail.com>
* 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