From: Tom Lane [EMAIL PROTECTED]
You've provided no evidence that this is a bad plan.
Looks like I didn't take the time to understand properly what the explains were
showing.
In particular, the plan you seem to think would be better
would involve
an estimated 153 iterations of the
Glyn Astill [EMAIL PROTECTED] writes:
Does anyone know how I can change what I'm doing to get pgsql to pick a
better plan?
You've provided no evidence that this is a bad plan.
In particular, the plan you seem to think would be better would involve
an estimated 153 iterations of the cost-15071
Anyone?
--- On Fri, 5/12/08, Glyn Astill [EMAIL PROTECTED] wrote:
From: Glyn Astill [EMAIL PROTECTED]
Subject: [GENERAL] Planner picking topsey turvey plan?
To: pgsql-general@postgresql.org
Date: Friday, 5 December, 2008, 2:23 PM
Hi people,
Does anyone know how I can change what I'm
what does explain analyze yourqueryhere say?
On Sat, Dec 6, 2008 at 1:33 PM, Glyn Astill [EMAIL PROTECTED] wrote:
Anyone?
--- On Fri, 5/12/08, Glyn Astill [EMAIL PROTECTED] wrote:
From: Glyn Astill [EMAIL PROTECTED]
Subject: [GENERAL] Planner picking topsey turvey plan?
To: pgsql-general
--- On Sat, 6/12/08, Scott Marlowe [EMAIL PROTECTED] wrote:
From: Scott Marlowe [EMAIL PROTECTED]
Subject: Re: [ADMIN] [GENERAL] Planner picking topsey turvey plan?
To: [EMAIL PROTECTED]
Cc: pgsql-general@postgresql.org, [EMAIL PROTECTED]
Date: Saturday, 6 December, 2008, 8:35 PM
what does
Hi people,
Does anyone know how I can change what I'm doing to get pgsql to pick a better
plan?
I'll explain what I've done below but please forgive me if I interpret the
plans wrong as I try to describe, I've split it into 4 points to try and ease
the mess of pasting in the plans..
1) I've
