| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | mlw <markw(at)mohawksoft(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nicolas Bazin <nbazin(at)ingenico(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Postgresql backend to perform vacuum automatically |
| Date: | 2002-03-05 18:06:30 |
| Message-ID: | 200203051806.g25I6Uv28927@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Are there tables that track information that would be useful for guiding
> vacuum? Could I write a program which queries some statistical tables and and
> knows which tables need to be vacuumed?
>
> If the info is around, I could whip up something pretty easily, I think.
Sure, Jan's new statistics tables in 7.2 had just that info.
test=> \d pg_stat_user_tables
View "pg_stat_user_tables"
Column | Type | Modifiers
---------------+---------+-----------
relid | oid |
relname | name |
seq_scan | bigint |
seq_tup_read | bigint |
idx_scan | numeric |
idx_tup_fetch | numeric |
n_tup_ins | bigint |
n_tup_upd | bigint |
n_tup_del | bigint |
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mlw | 2002-03-05 18:16:25 | Re: Postgresql backend to perform vacuum automatically |
| Previous Message | Bruce Momjian | 2002-03-05 18:02:16 | Re: Undocumented feature costs a lot of performance in COPY |