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

Re: Database size

From: "J6M" <j6m(at)adm(dot)estp(dot)fr>
To: "Francisco Reyes" <lists(at)stringsutils(dot)com>,"choksi" <choksi(dot)dhaval(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Database size
Date: 2007-06-18 08:39:15
Message-ID: 075101c7b188$23e46df0$1500020a@eden.fr (view raw or flat)
Thread:
Lists: pgsql-performance
Hello group,

Moreover a reindex (REINDEX <name of your database> while in pgsql) followed 
by an ANALYZE will claim more space.

Regards
J6M
----- Original Message ----- 
From: "Francisco Reyes" <lists(at)stringsutils(dot)com>
To: "choksi" <choksi(dot)dhaval(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Sent: Friday, June 15, 2007 7:15 PM
Subject: Re: [PERFORM] Database size


> choksi writes:
>
>> I had a database which uses to hold some 50 Mill records and disk
>> space used was 103 GB. I deleted around 34 Mill records but still the
>> disk size is same. Can some on please shed some light on this.
>
> When records are deleted they are only marked in the database.
> When you run vacuum in the database that space will be marked so new data 
> can use the space.
>
> To lower the space used you need to run "vacuum full".
> That however can take a while and I think it will lock the database for 
> some operations.


In response to

pgsql-performance by date

Next:From: Sabin CoandaDate: 2007-06-18 13:09:05
Subject: Re: Parsing VACUUM VERBOSE
Previous:From: Tom LaneDate: 2007-06-16 15:07:08
Subject: Re: determining maxsize for character varying

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