Re: SELECT MIN, MAX took longer time than SELECT COUNT, MIN, MAX - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: SELECT MIN, MAX took longer time than SELECT COUNT, MIN, MAX
Date
Msg-id 20060120172026.GF20182@pervasive.com
Whole thread Raw
In response to SELECT MIN, MAX took longer time than SELECT COUNT, MIN, MAX  (K C Lau <kclau60@netvigator.com>)
Responses Re: SELECT MIN, MAX took longer time than SELECT COUNT, MIN, MAX  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: SELECT MIN, MAX took longer time than SELECT  (K C Lau <kclau60@netvigator.com>)
List pgsql-performance
On Fri, Jan 20, 2006 at 12:35:36PM +0800, K C Lau wrote:

Here's the problem... the estimate for the backwards index scan is *way*
off:

>      ->  Limit  (cost=0.00..1.26 rows=1 width=4) (actual
> time=200032.928..200032.931 rows=1 loops=1)
>            ->  Index Scan Backward using pk_log on
> log  (cost=0.00..108047.11 rows=86089 width=4) (actual
> time=200032.920..200032.920 rows=1 loops=1)
>                  Filter: (((create_time)::text < '2005/10/19'::text) AND
> (logsn IS NOT NULL))
>  Total runtime: 200051.701 ms

BTW, these queries below are meaningless; they are not equivalent to
min(logsn).

> esdt=> explain analyze select LogSN from Log where create_time <
> '2005/10/19' order by create_time limit 1;
>
>  Limit  (cost=0.00..0.98 rows=1 width=31) (actual time=0.071..0.073 rows=1
> loops=1)
>    ->  Index Scan using idx_logtime on log  (cost=0.00..84649.94
> rows=86089 width=31) (actual time=0.063..0.063 rows=1 loops=1)
>          Index Cond: ((create_time)::text < '2005/10/19'::text)
>  Total runtime: 0.182 ms
>
> esdt=> explain analyze select LogSN from Log where create_time <
> '2005/10/19' order by create_time desc limit 1;
>  Limit  (cost=0.00..0.98 rows=1 width=31) (actual time=0.058..0.061 rows=1
> loops=1)
>    ->  Index Scan Backward using idx_logtime on log  (cost=0.00..84649.94
> rows=86089 width=31) (actual time=0.051..0.051 rows=1 loops=1)
>          Index Cond: ((create_time)::text < '2005/10/19'::text)
>  Total runtime: 0.186 ms
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Autovacuum / full vacuum (off-topic?)
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Autovacuum / full vacuum (off-topic?)