Il giorno dom, 16/07/2006 alle 11.08 -0700, Joe Conway ha scritto:
Gabriele Turchi wrote:
registrazioni. Given that performance degrades so quickly as records are
inserted into registrazioni, I'm wondering if you're missing an index.
What indexes do you have on registrazioni?
Joe
Gabriele Turchi wrote:
Il giorno sab, 15/07/2006 alle 13.04 -0700, Joe Conway ha scritto:
way to do this? If the performance in the better case is 50 times faster
than the worse case, during an hour (50/100 record inserted in
"registrazioni") how much the performance can fall before the new
"ANALYZE" is run? Otherwise, running ANALYZE more frequently can badly
affect the overall performance?
One thing I noticed is that in both plans there is a seq scan onWhy not just periodically (once an hour?) run "ANALYZE registrazioni;"
during the day. This will only update the statistics, and should be very
low impact.
This is my "solution" too... but: is enough? Or else: there is a betterduring the day. This will only update the statistics, and should be very
low impact.
way to do this? If the performance in the better case is 50 times faster
than the worse case, during an hour (50/100 record inserted in
"registrazioni") how much the performance can fall before the new
"ANALYZE" is run? Otherwise, running ANALYZE more frequently can badly
affect the overall performance?
registrazioni. Given that performance degrades so quickly as records are
inserted into registrazioni, I'm wondering if you're missing an index.
What indexes do you have on registrazioni?
Joe
performance (under 8.0) was "more than enough". I thought that creating
an index on a table with no more than some hundred of records was not
useful...
My biggest doubt is anyway related to the very big difference between
the plans in 8.0 and 8.1 under the same conditions.
Thank you,
Gabriele
