Re: The optimizer is too smart for me - How can I trick it?

From: "Peter Vanderborght" <peter(dot)vanderborght(at)taatu(dot)com>
To: "'Adam Rich'" <adam(dot)r(at)sbcglobal(dot)net>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: The optimizer is too smart for me - How can I trick it?
Date: 2008-05-30 15:28:41
Message-ID: 007901c8c269$d7a5c8a0$88c8a8c0@TAATU.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


GREAT!!!
Just "offset 0" in the subquery did the trick!

I had already been playing with a stored proc, but that's way more messy
than this.

Thanks a million!
Peter

-----Original Message-----
From: Adam Rich [mailto:adam(dot)r(at)sbcglobal(dot)net]
Sent: 30 May 2008 17:14
To: peter(dot)vanderborght(at)taatu(dot)com; pgsql-general(at)postgresql(dot)org
Subject: RE: [GENERAL] The optimizer is too smart for me - How can I trick
it?

> I've implemented Depesz's running total function
> (http://www.depesz.com/index.php/2007/08/17/rownum-anyone-cumulative-
> sum-in-
> one-query/) in my DB, which works great.
> Now what I want to do is get the running total for a certain statement
> and then do a subselect on that result so to get a non-zero start on a
> function.
>
> Instead, the optimizer sees what I'm trying to do, moves the where
> clause inside the subquery and my output becomes
>
> What can I do to tell the optimizer to keep its hands off my query or
> at least get it to not optimize?
>

I think if you add a LIMIT/OFFSET clause to your subquery, the planner
will leave it alone.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Clodoaldo 2008-05-30 15:43:56 Query planning configuration and solid state drives
Previous Message Adam Rich 2008-05-30 15:13:49 Re: The optimizer is too smart for me - How can I trick it?