From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alessandro Baretta <a(dot)baretta(at)barettadeit(dot)com> |
Cc: | Matteo Beccati <php(at)beccati(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 500x speed-down: Wrong query plan? |
Date: | 2006-01-09 18:41:05 |
Message-ID: | 6719.1136832065@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Alessandro Baretta <a(dot)baretta(at)barettadeit(dot)com> writes:
> Matteo Beccati wrote:
>> Are you sure that you recentrly ANALYZED the table "ubicazione"? If so,
>> try to increase statistics for the id_ente column.
> No, this is not the problem. I increased the amount of statistics with ALTER
> TABLE ... SET STATISTICS 1000, which is as much as I can have.
What Matteo wanted to know is if you'd done an ANALYZE afterward. ALTER
TABLE SET STATISTICS doesn't in itself update the statistics.
What do you get from
EXPLAIN SELECT * FROM articolo WHERE articolo.xdbs_modified > '2006-01-08 18:25:00+01';
I'm curious to see how many rows the planner thinks this will produce,
and whether it will use the index or not.
Also, I gather from the plan choices that the condition id_ente = 'dmd'
isn't very selective ... what fraction of the rows in each table
satisfy that?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alessandro Baretta | 2006-01-09 18:50:19 | Re: 500x speed-down: Wrong query plan? |
Previous Message | peter royal | 2006-01-09 17:23:15 | Re: help tuning queries on large database |