From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
---|---|
To: | Phillip Smith <phillips(at)weatherbeeta(dot)com(dot)au>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: SELECT Aggregate |
Date: | 2006-06-30 04:48:15 |
Message-ID: | 20060630044815.60284.qmail@web31805.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> Well whatdyaknow?? Being a Postgres newbie I hadn't even played with indexes
> yet. They're awesome!!
> Using Richard's suggestion of the Sub-Select in the COLUMN list, combined
> with adding some indexes, I can now return this in under 5 seconds!
Also, another way to improve preformance will be to analyze the affected tables. Analyze will
ensure that the query planner has accurate statics by which it will use in picking fastest
possible query.
If you ever plan on updating or deleting records. You will also need to vacuum the table. And an
additional measure of maintance would be to re-index the database.
All of this is listing in the postgresql manual. If you really want to ensure the best possible
speeds, it will be an important step to take.
Regards,
Richard Broersma Jr.
From | Date | Subject | |
---|---|---|---|
Next Message | Jure Kodzoman | 2006-06-30 09:51:25 | Re: Data Entry and Query forms |
Previous Message | Phillip Smith | 2006-06-30 02:55:05 | Re: SELECT Aggregate |