| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Serious performance problem |
| Date: | 2001-10-31 05:41:56 |
| Message-ID: | 4.2.0.58.20011031064030.00d91620@pop.freesurf.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>Why not create an extra "statistics" table which is updated automatically
>through triggers in your original table? That way, you will always get
>up-to-date INSTANT query results no matter how huge your original table is.
>
>And, don't forget that the only way MS SQL can achieve the better performance
>here is through mercilessly hogging ressources. In a complex database
>environment with even larger tables, the performance gain in MS SQL would be
>minimal (my guess).
Definitely. This is a design optimization problem not an index problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-10-31 05:58:46 | Re: timetz regression test is showing several DST-related |
| Previous Message | Horst Herb | 2001-10-31 03:37:29 | Re: Serious performance problem |