From: | Mario Weilguni <mweilguni(at)sime(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Self-generating statistics? |
Date: | 2002-10-21 06:23:33 |
Message-ID: | 200210210823.33744.mweilguni@sime.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Something that might be worth considering:
Many of the performance problems on pgsql-general seem to be related to the fact that no analyze is performed after the creation on the tables, so
maybe this might be an option to fix that (in future releases): when a table has no statistics at all, and the first seq-scan on the table is
performed, it might improve further performance if this seq-scan is used to get table statistics too. This should not be too expensive since reading the
table has to be done only once. Further queries will have at least preliminary statistics at hand.
I'm not sure how (CPU) expensive statistic-gathering is, but if most of the work is reading the tuples, it might be a win to do this.
Regards,
Mario Weilguni
From | Date | Subject | |
---|---|---|---|
Next Message | Ludwig Lim | 2002-10-21 07:04:58 | Default cost variables in postgresql.conf |
Previous Message | Tom Lane | 2002-10-18 01:37:27 | Re: Max time queries |