Re: Query only slow on first run

[Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>]

"Dave Dutcher" <dave(at)tridecap(dot)com> writes:
> ... According to the explain analyze
> there are only 646 rows in posts which match your criteria, so it does seem
> like scanning posts first might be the right thing to do. 

No, that's not right.  What the output actually shows is that only 646
posts rows were needed to produce the first 200 aggregate rows, which was
enough to satisfy the LIMIT.  The planner is evidently doing things this
way in order to exploit the presence of the LIMIT --- if it had to
compute all the aggregate results it would likely have picked a
different plan.

			regards, tom lane