| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: An unresolved performance problem. |
| Date: | 2003-05-07 15:26:52 |
| Message-ID: | 200305070826.52382.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-performance pgsql-sql |
Achilleus,
> My systems are (rather usual) linux/freebsd and the costs defined (by
> default) in postgresql.conf worked well for all queries except
> a cursed query on a cursed table.
> So i start to believe its an estimation selectivity
> problem.
We can probably fix the problem by re-writing the query then; see my previous
example this weekend about overdetermining criteria in order to force the use
of an index.
How about posting the query and the EXPLAIN ANALYZE results?
--
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mendola Gaetano | 2003-05-07 15:36:29 | Re: [SQL] An unresolved performance problem. |
| Previous Message | Tom Lane | 2003-05-07 14:11:21 | Re: float8 errors in HEAD... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mendola Gaetano | 2003-05-07 15:36:29 | Re: [SQL] An unresolved performance problem. |
| Previous Message | Ryan | 2003-05-07 14:43:28 | Re: Yet another 'why does it not use my index' question. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mendola Gaetano | 2003-05-07 15:36:29 | Re: [SQL] An unresolved performance problem. |
| Previous Message | Ries van Twisk | 2003-05-07 15:07:55 | array in a reference |