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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: VACUUM FULL does not works.......


  • From: "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com>
  • To: "asif ali" <asif_icrossing(at)yahoo(dot)com>
  • Cc: pgsql-performance(at)postgresql(dot)org
  • Subject: Re: VACUUM FULL does not works.......
  • Date: Wed, 6 Dec 2006 23:17:10 +0530
  • Message-id: <a97c77030612060947g7265aba0nef60588f2070cae(at)mail(dot)gmail(dot)com>

On 12/6/06, asif ali <asif_icrossing(at)yahoo(dot)com> wrote:
Hi,
 I have a "product" table having 350 records. It takes approx 1.8 seconds to
get all records from this table. I copies this table to a "product_temp"
table and run the same query to select all records; and it took 10ms(much
faster).
 I did "VACUUM FULL" on "product" table but It did not work.

 I checked the file size of these two tables.
 "product" table's file size is "32mb" and
 "product_temp" table's file size is "72k".

 So, it seems that "VACUUM FULL" is not doing anything.
 Please suggest.

It is desirable that PostgreSQL version be reported in problem descriptions.

Older versions of pgsql had problem of index bloat. It is interesting to
find out why VACUUM FULL does not work in your case(wait for the experts) ,
but most probably CLUSTERING the table on primary key is going to
solve the query performance problem (temporarily)


 asif ali
 icrossing inc.

 ________________________________
Have a burning question? Go to Yahoo! Answers and get answers from real
people who know.



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group