From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: slow count in window query |
Date: | 2009-07-17 14:48:33 |
Message-ID: | 162867790907170748k59efd591wd47703d780b4bf65@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/7/17 Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>:
> 2009/7/17 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
>> Hello
>>
>> look on:
>> postgres=# explain select count(*) over () from x;
>> QUERY PLAN
>> -------------------------------------------------------------
>> WindowAgg (cost=0.00..265.00 rows=10000 width=0)
>> -> Seq Scan on x (cost=0.00..140.00 rows=10000 width=0)
>> (2 rows)
>>
>> Time: 1,473 ms
>> postgres=# explain select count(*) over (order by a) from x;
>> QUERY PLAN
>> ------------------------------------------------------------------------
>> WindowAgg (cost=0.00..556.25 rows=10000 width=4)
>> -> Index Scan using gg on x (cost=0.00..406.25 rows=10000 width=4)
>> (2 rows)
>>
>> but
>> query1: 160ms
>> query2: 72ms
>
> Well, how about "select a from x order by a"?
> I wonder if index scan affects more than windowagg.
>
select a from x -> 42ms
select a from x order by a -> 50ms
all data are from cache.
> --
> Hitoshi Harada
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-07-17 14:58:11 | Re: pg_stat_activity.application_name |
Previous Message | Pavel Stehule | 2009-07-17 14:43:37 | Re: slow count in window query |