From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
---|---|
To: | Mahesh Shinde <mahesh(dot)shinde(at)hovservices(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Default autovacuum settings too conservative |
Date: | 2006-02-08 13:38:08 |
Message-ID: | 43E9F440.1080001@logix-tt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
Hi, Mahesh,
Mahesh Shinde wrote:
> Does vacuum improves the performance of the database search.. As if now I
> have a table who is having a records 70 lac and daily appx 10-15 thousand
> rows get added. so please let me know which type of vacuum I should prefer.
> I am accessing a data using java application which is hosted on the same
> database server.
I don't know what "70 lac" means.
But if you only add to the table, and never update or delete, vacuum
brings nothing for performance. (Although it is necessary for TID
wraparound prevention.)
However, if your often do range queries on an index that does not
correspond to the insertion order, you may benefit from CLUSTERing on
that index from time to time.
Hth,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Deugau | 2006-02-08 15:52:22 | Re: Actual expression of a constraint |
Previous Message | Bradley Kieser | 2006-02-08 11:07:10 | Re: Postgresql 8.0 or 8.1 vs. latest Red Hat RPM |
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Costello | 2006-02-08 13:54:51 | optimizing away join when querying view |
Previous Message | Markus Schaber | 2006-02-08 11:05:10 | Re: Default autovacuum settings too conservative |