From: | yves(at)mail2(dot)vlaanderen(dot)net |
---|---|
To: | lockhart(at)fourpalms(dot)org |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: [SQL] Re: why the DB file size does not reduce when 'delete'the data in DB? |
Date: | 2001-03-16 01:28:46 |
Message-ID: | 20010316022846.A3804@asua2.vlaanderen.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
On Fri, Mar 16, 2001 at 12:01:36AM +0000, Thomas Lockhart wrote:
> > > You are not quite factually correct above, even given your definition of
> > > "bug". PostgreSQL does reuse deleted record space, but requires an
> > > explicit maintenance step to do this.
> > Could you tell us what that maintenance step is? dumping the db and restoring into a fresh one ? :/
>
> :) No, "VACUUM" is your friend for this. Look in the reference manual
> for details.
>
> - Thomas
I'm having this problem:
I have a database that is 3 megabyte in size (measured using pg_dump). When
i go to the corresponding data directory (eg du -h data/base/mydbase), it
seems the real disk usage is 135 megabyte! Doing a VACUUM doesn't really
change the disk usage.
Also query & updating speed increases when i dump all data and restore
it into a fresh new database.
I'm running postgresql-7.0.2-6 on a Debian potato.
-Yves
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-16 01:42:02 | Re: Beta6 for Tomorrow? |
Previous Message | Philip Warner | 2001-03-16 01:20:04 | Re: Performance monitor signal handler |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2001-03-16 04:18:52 | Re: Re: Normalization is always good? |
Previous Message | Christof Glaser | 2001-03-16 00:48:51 | Re: Re: Normalization is always good? |