| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Ives Landrieu <ives(dot)landrieu(at)ua(dot)ac(dot)be> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Strange cost computation? |
| Date: | 2002-10-30 15:59:56 |
| Message-ID: | 20021030075807.L31345-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 29 Oct 2002, Ives Landrieu wrote:
> Hi,
>
> Can anybody explain the following results when using EXPLAIN,
> one time with enable_seqscan=on and one time with enable_seqscan=off.
> What I don't understand is that the nodes created are the same
> (index scan, seq scan), but the costs differ.
Enable seq scan actually just sets a large cost disbenefit to seq scans.
Is alias96.STATUS indexed?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-10-30 16:12:12 | Re: Strange cost computation? |
| Previous Message | Stephan Szabo | 2002-10-30 15:53:22 | Re: float output precision questions |