| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Simon Hardingham" <simon(at)netxtra(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: query optimiser changes 6.5->7.0 |
| Date: | 2000-06-02 02:39:47 |
| Message-ID: | 9879.959913587@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Simon Hardingham" <simon(at)netxtra(dot)net> writes:
> I have run explain on the query and it shows that it is just
> performed a sequential scan on version 7.0
> Seq Scan on gazet (cost.....)
> On the old version (6.5.1) it reports
> Index Scan using gazet_index on gazet (cost=....
> Any suggestions as to how I can improve performance on this databases new
> server?
Unfortunately you have been careful to suppress any information that
might actually let someone give you useful advice ;-). There are
several threads in the archives about undesirable index-vs-sequential-
scan choices in 7.0; check pgsql-sql as well as pgsql-general for the
last month or so.
Also, 7.0.1, propagating now to an archive near you, contains some
fudge-factor twiddling to make it more willing to choose an indexscan.
We shall soon find out whether that made things better or worse for
typical uses...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-02 02:42:40 | Re: interval questions |
| Previous Message | Michael Blakeley | 2000-06-02 02:29:54 | Re: interval questions |