From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Tim Perdue <tperdue(at)valinux(dot)com> |
Cc: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, pgsql-hackers(at)hub(dot)org |
Subject: | Re: 7.0.2 issues / Geocrawler |
Date: | 2000-07-12 17:01:07 |
Message-ID: | Pine.BSF.4.21.0007121400150.1325-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 12 Jul 2000, Tim Perdue wrote:
> "Ross J. Reedstrom" wrote:
> > Mike Mascari gave you a detailed answer to that, which you seemd to just blow
> > off, based on you guesstimate that it would run too long:
>
> That is a separate issue - unrelated to this performance issue and it
> was not "blown" off, I was merely making a comment.
>
> > Right, as your explain output showed: the planner is picking this index
> > and using it. I'd guess that your time is getting lost in the sort step.
>
> I think you're probably right. It's hard to imagine that sorting is that
> much slower, but it's hard to say.
just curious, but what if you remove the ORDER BY, just to test ... is it
that much faster without then with? Just want to narrow down *if* its a
sorting issue or not, that's all ...
If it is a sorting issue, what if you raise the -S value?
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB | 2000-07-12 17:18:44 | AW: 7.0.2 issues / Geocrawler |
Previous Message | Tim Perdue | 2000-07-12 17:00:14 | Re: 7.0.2 issues / Geocrawler |