From: | jose fuenmayor <jafn82(at)gmail(dot)com> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to>, jose fuenmayor <jafn82(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: size of indexes and tables (more than 1GB) |
Date: | 2005-08-30 13:26:16 |
Message-ID: | 69f2062a0508300626f33aa45@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
i waited like 11 hours and it doesn't finish, where is the FSM setting
postgreSQL.conf?
On 8/30/05, Bruno Wolff III <bruno(at)wolff(dot)to> wrote:
>
> On Tue, Aug 30, 2005 at 08:38:03 -0400,
> jose fuenmayor <jafn82(at)gmail(dot)com> wrote:
> > i am using postgreSql 8.0.3 i've try vacuum "vacuum full" the hole
> database
> > but it takes too long, seems it will never be finished, i've tried
> "vacuum
> > <table_name>" and the table remains nearly the same as isee i my PGDATA
> > directory. is this normal? . is there something i can do ?
>
> Have you tried VACUUM FULL on just that table?
>
> It may be that your FSM setting isn't high enough to remove all of the
> dead tuples with a normal vacuum.
>
> How long did you wait when you tried to vacuum full the whole database?
>
Another option is to use the CLUSTER command on the big table. If that
> table is mostly dead tuples, cluster may run faster than vacuum full.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas F. O'Connell | 2005-08-30 14:01:36 | Re: sqlstate 02000 while declaring cursor/freeing statement |
Previous Message | KALODIKIS THODORIS | 2005-08-30 13:07:14 | Unsubscribe |