-
Notifications
You must be signed in to change notification settings - Fork 137
Open
Description
The v1 - Vacuum: current activity query is broken under postgresql 17:
➤ 2025-10-10 06:24 AM EDT replica/postgres
=# :dba
Menu:
0 – Node and current database information: primary/replica, lag, database size, temporary files, etc.
1 – Databases: size, stats
2 – Tables: table/index/TOAST size, number of rows
3 – Load profile
a1 – Current activity: count of current connections grouped by database, username, state
b1 – Table bloat (estimated)
b2 – B-tree index bloat (estimated)
b3 – Table bloat (requires pgstattuple; expensive)
b4 – B-tree indexes bloat (requires pgstattuple; expensive)
b5 – Tables and columns without stats (so bloat cannot be estimated)
e1 – Extensions installed in current database
i1 – Unused and rarely used indexes
i2 – Redundant indexes
i3 – Foreign keys with missing or bad indexes
i4 – Invalid indexes
i5 – Cleanup unused and redundant indexes – DO & UNDO migration DDL
l1 – Lock trees (lightweight)
l2 – Lock trees, detailed (based on pg_blocking_pids())
p1 – [EXP] Alignment padding: how many bytes can be saved if columns are reordered?
r1 – Create user with random password (interactive)
r2 – Alter user with random password (interactive)
s1 – Slowest queries, by total time (requires pg_stat_statements)
s2 – Slowest queries report (requires pg_stat_statements)
t1 – Postgres parameters tuning
v1 – Vacuum: current activity
v2 – VACUUM progress and autovacuum queue
q – Quit
Type your choice and press <Enter>:
v1
psql:/var/lib/postgresql/postgres_dba/sql/v1_vacuum_activity.sql:68: ERROR: column p.num_dead_tuples does not exist
LINE 24: round(100.0 * p.num_dead_tuples / p.max_dead_tuples, 2) ...
^
Press <Enter> to continue…
Metadata
Metadata
Assignees
Labels
No labels