From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Brian Herlihy <btherl(at)yahoo(dot)com(dot)au> |
Cc: | Postgresql Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Vacuum goes worse |
Date: | 2007-10-17 03:19:51 |
Message-ID: | 20071016201951.267b066d@scratch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, 16 Oct 2007 17:03:39 -0700 (PDT)
Brian Herlihy <btherl(at)yahoo(dot)com(dot)au> wrote:
> Would it make sense to show the FSM stats for individual table
> vaccums as well? I'm wondering if the reason they aren't shown is
> because it wouldn't be useful or isn't practical, or just that it
> hasn't been done.
I am not sure how useful it would be as the FSM is global. However what
would be useful is something like VACUUM SUMMARY, where I could get
"just" the stats instead of all the other output that comes along with
VERBOSE.
Joshua D. Drake
>
> Brian
>
> ----- Original Message ----
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>
> If you're talking about the FSM statistics display, that only gets
> printed by a database-wide VACUUM (one that doesn't name a specific
> table).
>
> regards, tom lane
>
>
>
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 5: don't forget to increase
> your free space map settings
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | Marcin Stępnicki | 2007-10-17 05:32:47 | Re: using a stored proc that returns a result set in a complex SQL stmt |
Previous Message | Tom Lane | 2007-10-17 01:16:01 | Re: Vacuum goes worse |