From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Vacuum columns in statistics tables |
Date: | 2006-11-23 16:48:56 |
Message-ID: | 200611231648.kANGmuf01801@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> Is there a reason why the vacuum tracking columns in pg_stat_all_tables
> etc. were added before the existing columns? I find this to be a very
> inconvenient regression because I use the counter columns much more
> often. What is the rationale for that?
Agreed, that is quite odd:
View "pg_catalog.pg_stat_all_tables"
Column | Type | Modifiers
------------------+--------------------------+-----------
relid | oid |
schemaname | name |
relname | name |
last_vacuum | timestamp with time zone |
last_autovacuum | timestamp with time zone |
last_analyze | timestamp with time zone |
last_autoanalyze | timestamp with time zone |
seq_scan | bigint |
seq_tup_read | bigint |
idx_scan | bigint |
idx_tup_fetch | bigint |
n_tup_ins | bigint |
n_tup_upd | bigint |
n_tup_del | bigint |
My only guess is it was done because the vacuum information more a
characteristic of the relation than the statistics. However, I agree
having them later makes more sense.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-11-23 16:49:29 | Re: [PERFORM] Direct I/O issues |
Previous Message | Bruce Momjian | 2006-11-23 16:45:42 | Re: Hierarchical Queries status? |