| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Vincenzo Romano <vincenzo(dot)romano(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to avoid "Seq Scans"? |
| Date: | 2007-08-29 09:31:18 |
| Message-ID: | 20070829093118.GB29716@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 29, 2007 at 11:15:21AM +0200, Vincenzo Romano wrote:
> This loop is increadibly slow. Infact the friendly explain tells me
> that:
Is it wrong? Have you have run with seq_scan disabled to see if an
index scan is actually faster? If so, then perhaps your
random+pagE_cost needs adjusting.
Also, your query can't use an index anyway, for that you'd need an
index on (f2,f3).
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jens Reufsteck | 2007-08-29 10:15:49 | Performance issue with nested loop |
| Previous Message | A. Kretschmer | 2007-08-29 09:29:21 | Re: How to avoid "Seq Scans"? |