Re: Postgres Load Profile
| От | Ron Johnson |
|---|---|
| Тема | Re: Postgres Load Profile |
| Дата | |
| Msg-id | CANzqJaBpi-VMu9xOj-qksKoLLoggZNTi13ZUu5eea8M5Rc6eow@mail.gmail.com обсуждение исходный текст |
| Ответ на | Postgres Load Profile (Sam Stearns <sam.stearns@dat.com>) |
| Ответы |
Re: Postgres Load Profile
|
| Список | pgsql-admin |
On Mon, Nov 3, 2025 at 5:56 PM Sam Stearns <sam.stearns@dat.com> 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)
- 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!
В списке pgsql-admin по дате отправления: