Skip site navigation (1) Skip section navigation (2)

Re: size of indexes and tables (more than 1GB)

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 (view raw or flat)
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.
>

In response to

Responses

pgsql-admin by date

Next:From: Thomas F. O'ConnellDate: 2005-08-30 14:01:36
Subject: Re: sqlstate 02000 while declaring cursor/freeing statement
Previous:From: KALODIKIS THODORISDate: 2005-08-30 13:07:14
Subject: Unsubscribe

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group