Re: How do query optimizers affect window functions

From: Tianyin Xu <tixu(at)cs(dot)ucsd(dot)edu>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: How do query optimizers affect window functions
Date: 2012-11-14 22:16:29
Message-ID: CABBDWwehiNbVwSDpYA4b4U-eKVXxoqUfGSVUW3MRm-O6WdZzCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks a lot, Jeff!

On Wed, Nov 14, 2012 at 11:59 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:

> On Wed, Nov 14, 2012 at 12:12 AM, Tianyin Xu <tixu(at)cs(dot)ucsd(dot)edu> wrote:
> > Hi, Postgresql,
> >
> > I want to understand how the query optimizers affect the output of the
> > window functions.
>
> Use "EXPLAIN".
>
> One is an index scan, one is a bitmap scan. They return rows in a
> different order.
>
> ..
>
> > I don't understand why the results are different. Intuitively, the
> queries
> > show return the same results no matter what plan the optimizer choose.
>
> My intuition is that the query should refuse to run at all, because
> the results are order dependent and you haven't specified an ordering.
>
>
What do you mean by "refused to run"? You mean we have to specify the order
when using the window functions? Could you explain more?

Thanks!

> Cheers,
>
> Jeff
>

--
Tianyin XU,
http://cseweb.ucsd.edu/~tixu/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message VB N 2012-11-14 22:34:09 Re: FATAL: index contains unexpected zero page at block
Previous Message John R Pierce 2012-11-14 22:08:18 Re: High SYS CPU - need advise