Re: How to get started hacking on pgsql - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: How to get started hacking on pgsql
Date
Msg-id 1070572243.3543.9.camel@fuji.krosing.net
Whole thread Raw
In response to Re: How to get started hacking on pgsql  (Hannu Krosing <hannu@tm.ee>)
List pgsql-hackers
Hannu Krosing kirjutas N, 04.12.2003 kell 23:01:

> 
> > Where should I be looking in the code?
> 
> Try to find where the modified query is tested for. It's probably be
> inside the optimizer, as index scan + no sort is not always faster than
> seq scan + sort, as shown by the same query after vacuum analyze (on an
> empty table)

OTOH, it may be that all combinations of sort and index and where are
not watched in the optimiser proper at all (too compliaced and/or too
costly), but a keyhole optimiser is run over its resulting  "best" plan
to remove redundant sorts (but it misses combinations of sort and where
like the one in your example)

---------------
Hannu



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: How to get started hacking on pgsql
Next
From: Alvar Freude
Date:
Subject: bytea, index and like operator again and detailed report