Re: Query works when kludged, but would prefer "best practice" solution
От | Carlo Stonebanks |
---|---|
Тема | Re: Query works when kludged, but would prefer "best practice" solution |
Дата | |
Msg-id | E2AE41090F56435280513F7E6B3AA78C@serenity обсуждение исходный текст |
Ответ на | Re: Query works when kludged, but would prefer "best practice" solution ("Merlin Moncure" <mmoncure@gmail.com>) |
Ответы |
Re: Query works when kludged, but would prefer "best practice" solution
|
Список | 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@gmail.com] Sent: September 17, 2007 8:03 PM To: Carlo Stonebanks Cc: pgsql-performance@postgresql.org Subject: Re: [PERFORM] Query works when kludged, but would prefer "best practice" solution On 9/17/07, Carlo Stonebanks <stonec.register@sympatico.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
В списке pgsql-performance по дате отправления: