hot updates and fillfactor

From: Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: hot updates and fillfactor
Date: 2024-03-19 08:58:20
Message-ID: CAA5-nLAik_24keWVOOSsdPMKhPg4RR6NK5TK8MuJKNBN13hxDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I do not understand why hot_updates value is not 0 for pg_database? Given
that reloptions is empty for this table that means it has a default value
of 100%

Regards,

Fabrice

SELECT
relname AS table_name,
seq_scan AS sequential_scans,
idx_scan AS index_scans,
n_tup_ins AS inserts,
n_tup_upd AS updates,
n_tup_hot_upd AS hot_updates
FROM
pg_stat_all_tables
ORDER BY
hot_updates DESC;

table_name | sequential_scans | index_scans | inserts |
updates | hot_updates
-------------------------+------------------+-------------+---------+---------+-------------
pg_database | 5038104 | 187427486 | 3 |
16 | * 16*

postgres [1728332]=# select t.relname as table_name,
t.reloptions
from pg_class t
join pg_namespace n on n.oid = t.relnamespace
where t.relname in ('pg_database')
and n.nspname = 'pg_catalog';

table_name | reloptions
-------------+------------
pg_database |
(1 row)

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2024-03-19 09:01:02 Re: SQL:2011 application time
Previous Message Peter Eisentraut 2024-03-19 08:55:51 Re: UUID v7