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: 2006-12-06 17:47:10
Message-ID: a97c77030612060947g7265aba0nef60588f2070cae@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Casey Duncan 2006-12-06 17:58:37 Re: [PERFORM] Locking in PostgreSQL?
Previous Message Markus Schiltknecht 2006-12-06 17:45:56 Re: File Systems Compared