From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
Cc: | "Hartman, Matthew" <Matthew(dot)Hartman(at)krcc(dot)on(dot)ca>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Vacuum on the database versus individual tables. |
Date: | 2009-06-25 15:59:31 |
Message-ID: | 937d27e10906250859y698ffc14y9ef7cf88d85afd4b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/6/25 Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>:
> 2009/6/25 Hartman, Matthew <Matthew(dot)Hartman(at)krcc(dot)on(dot)ca>:
>> Windows XP, PostgreSQL 8.3.5, using pgAdmin III 1.8.4. It's the typical "Running vacuum on this table is recommended" dialog box.
>
> Well, it really has nothing to do with postgresql it self. Either it
> is a bug or property of PgAdmin, but I don't know.
> Either someone who knows more about pgadmin is going to respond here,
> or you have to ask on pgadmin list.
pgAdmin will advise vacuuming a table if there is a significant
discrepancy between the number of rows in the table and the value in
pg_class.reltuples. i forget the exact algorithm off-hand, but it
takes the size of the table into account, and is looking for a %age
difference between the value, not a set number of rows.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2009-06-25 16:00:29 | Re: planned recovery from a certain transaction |
Previous Message | Grzegorz Jaśkiewicz | 2009-06-25 15:52:00 | Re: Vacuum on the database versus individual tables. |