From: | "Carlo Stonebanks" <stonec(dot)register(at)sympatico(dot)ca> |
---|---|
To: | "'Merlin Moncure'" <mmoncure(at)gmail(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Query works when kludged, but would prefer "best practice" solution |
Date: | 2007-09-18 00:13:18 |
Message-ID: | E2AE41090F56435280513F7E6B3AA78C@serenity |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Well, there goes my dream of getting a recommendation that will deliver a
blinding insight into how to speed up all of my queries a thousand-fold.
Thanks Merlin!
-----Original Message-----
From: Merlin Moncure [mailto:mmoncure(at)gmail(dot)com]
Sent: September 17, 2007 8:03 PM
To: Carlo Stonebanks
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Query works when kludged, but would prefer "best
practice" solution
On 9/17/07, Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca> wrote:
> Hi all,
>
> Please see the section marked as "PROBLEM" in "ORIGINAL QUERY" plan below.
> You can see it's pretty slow. Oddly enough, an index for
facility_address_id
> is available but not being used, but I suspect it's questionable whether
it
> would be an improvement.
This looks like it might be the problem tom caught and rigged a solution to:
http://people.planetpostgresql.org/dfetter/index.php?/archives/134-PostgreSQ
L-Weekly-News-September-03-2007.html
(look fro band-aid).
If that's the case, the solution is to wait for 8.2.5 (coming soon).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2007-09-18 00:17:49 | Re: Query works when kludged, but would prefer "best practice" solution |
Previous Message | Merlin Moncure | 2007-09-18 00:03:19 | Re: Query works when kludged, but would prefer "best practice" solution |