I have this QUERY (below) that PostgreSQL 7.3.X servers run MUCH slower
than
the 7.1.3 server does. It makes sense that both servers have to do a
sequential scan over the ZIPCODE column. There are over 7,500 rows in the
LOCATIONS table.
Does anyone know what changed in the planner or optimizer? Can
t
think that 7500 rows should never take over a minute. PG 7.3.3 takes 9
minutes (the one time we waited for it to finish).
How many data pages could 7500 rows need? With 2 or 3 page reads, it can't
take up much memory or I/O to do that.
- Andrew
On Wed, 6 Aug 2003, Tom Lane wrote:
>
