Subject: Re: Make the planner smarter about idiosyncratic (or broken)
	ORM behaviour
From: Simon Riggs <simon@2ndQuadrant.com>
To: Frank =?ISO-8859-1?Q?J=F6rdens?= <frank@woome.com>
Cc: pgsql-sql@postgresql.org, Nic Ferrier <nferrier@woome.com>,
	Edward George <ed@woome.com>, Seb Potter <seb@woome.com>,
	Hannu Krosing <hannu@2ndquadrant.com>
In-Reply-To: <7d10d2df0905220233v3e54ab34lb9c3530fe3543a5c@mail.gmail.com>
References: <7d10d2df0905220233v3e54ab34lb9c3530fe3543a5c@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Date: Fri, 22 May 2009 11:40:03 +0100
Message-Id: <1242988803.27960.382.camel@ebony.2ndQuadrant>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit


On Fri, 2009-05-22 at 10:33 +0100, Frank Jördens wrote:
> Almost all of the 8k queries per second that are hitting our database
> are generated by a web development framework's ORM (Django), and some
> of the syntax there is quite mad. Possibly the worst tic exhibited by
> the translation layer is that if you filter a query on an object by
> more than one property on a related object it will create a join for
> each property:

It's a known issue that we're looking to work on in the next release.

Work started in 8.4, though was more complex than first appeared and we
didn't complete it in time for the dev deadline.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support