pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: pgsql-performance@postgresql.org
Subject: Re: any way to use indexscan to get last X values
Date: Mon, 16 Jun 2003 11:45:52 +0530
Message-ID: <3EEDADF0.29611.3901BC1@localhost> (raw)
In-Reply-To: <5.2.1.1.0.20030616002729.01bba2e0@127.0.0.1>
References: <23329.1055695990@sss.pgh.pa.us>

On 16 Jun 2003 at 0:37, Tomaz Borstnar wrote:
> 
> krtjavendan34=>  EXPLAIN ANALYZE SELECT thread, modifystamp, count(id) AS 
> tcount,abstime(modifystamp) AS latest, max(id) as maxid FROM tjavendan 
> WHERE approved='Y'  GROUP BY modifystamp, thread ORDER BY modifystamp desc, 
> thread desc limit 40;
>                                                                                 QUERY 
> PLAN
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>   Limit  (cost=0.00..97.13 rows=40 width=12) (actual time=1.07..48.71 
> rows=40 loops=1)
>     ->  Aggregate  (cost=0.00..20947.38 rows=8626 width=12) (actual 
> time=1.05..48.23 rows=41 loops=1)
>           ->  Group  (cost=0.00..20516.06 rows=86265 width=12) (actual 
> time=0.35..42.25 rows=843 loops=1)
>                 ->  Index Scan Backward using tjavendan_modstamp_thrd on 
> tjavendan  (cost=0.00..20084.73 rows=86265 width=12) (actual 
> time=0.34..31.29 rows=844 loops=1)
>                       Filter: (approved = 'Y'::bpchar)
>   Total runtime: 50.20 msec
> (6 rows)
> 
> Used to be between 5800 and 6741 msec before this patch!

Good that the patch works for you. But as I see there is an improvement in 
plan. Not nitpicking but what does actual performance difference between system 
before patch and after patch?

Bye
 Shridhar

--
QOTD:	"In the shopping mall of the mind, he's in the toy department."




view thread (10+ messages)  latest in thread

Message-ID: <3EEDADF0.29611.3901BC1@localhost>
Permalink:  ../3EEDADF0.29611.3901BC1@localhost/
Also on:    postgresql.org/message-id/3EEDADF0.29611.3901BC1@localhost

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: shridhar_daithankar@persistent.co.in
  Subject: Re: any way to use indexscan to get last X values
  In-Reply-To: <3EEDADF0.29611.3901BC1@localhost>
  References: <23329.1055695990@sss.pgh.pa.us> <3EEDADF0.29611.3901BC1@localhost>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox