| From: | Pierre-Frédéric Caillaud <lists(at)boutiquenumerique(dot)com> |
|---|---|
| To: | "Rod Taylor" <rbt(at)rbt(dot)ca>, "Valerie Schneider DSI/DEV" <Valerie(dot)Schneider(at)meteo(dot)fr> |
| Cc: | "Postgresql Performance" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Tuning queries on large database |
| Date: | 2004-08-04 15:50:56 |
| Message-ID: | opsb7sy618cq72hf@musicbox |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
>> not so bad for oracle. What about for PG ? How data is stored
I agree with the datatype issue. Smallint, bigint, integer... add a
constraint...
Also the way order of the records in the database is very important. As
you seem to have a very large static population in your table, you should
insert it, ordered by your favourite selection index (looks like it's
poste).
Also, you have a lot of static data which pollutes your table. Why not
create two tables, one for the current year, and one for all the past
years. Use a view to present a merged view.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Cave-Ayland | 2004-08-04 16:17:08 | Recursive PLPGSQL function? |
| Previous Message | Gaetano Mendola | 2004-08-04 15:34:56 | Re: Tuning queries on large database |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre-Frédéric Caillaud | 2004-08-04 15:53:27 | Re: Tuning queries on large database |
| Previous Message | Michael Adler | 2004-08-04 15:36:24 | Re: Performance Bottleneck |