pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Oleg Bartunov <oleg@sai.msu.su>
To: Magnus Hagander <mha@sollentuna.net>
Cc: Kris Kiger <kris@musicrebellion.com>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: [HACKERS] slow count() was: tsearch2 poor performance
Date: Mon, 4 Oct 2004 00:51:47 +0400 (MSD)
Message-ID: <Pine.GSO.4.58.0410040049020.14217@ra.sai.msu.su> (raw)
In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE475DE4@algol.sollentuna.se>
References: <6BCB9D8A16AC4241919521715F4D8BCE475DE4@algol.sollentuna.se>


Magnus


On Sun, 3 Oct 2004, Magnus Hagander wrote:

> >> Hey all, its me again.  If I do not do a count(product_id) on my
> >> tsearch2 queries, its actually really fast, for example;
> >>
> >
> >Hmm, I also really want to know  what's the difference ?
> >Postgresql 8.0beta3 on Linux 2.4.25
> >
> >tsearchd=# explain analyze select body from txt where
> >fts_index @@ to_tsquery('oil') limit 1000;
> >                                                           QUERY PLAN
> >---------------------------------------------------------------
> >-----------------------------------------------------------------
> > Limit  (cost=0.00..4027.67 rows=1000 width=315) (actual
> >time=0.053..14.662 rows=1000 loops=1)
> >   ->  Index Scan using fts_idx on txt  (cost=0.00..12083.02
> >rows=3000 width=315) (actual time=0.049..12.552 rows=1000 loops=1)
> >         Index Cond: (fts_index @@ '\'oil\''::tsquery)
> > Total runtime: 15.848 ms
> >(4 rows)
> >
> >tsearchd=# explain analyze select count(body) from txt where
> >fts_index @@ to_tsquery('oil') limit 1000;
> >
> >Didn't get result after 10 minutes :(
> >
>
> I think you're missing what LIMIT does.
>
> In the first query, it LIMITs the return from the index scan to 1000
> entries.
> In the second query, it LIMITs the return from the aggregate to 1000
> entries. The indexscan will include all matches, send then to count(),
> which returns 1 row only, which LIMIT is then applied to.
>

Thanks for explanation. I suspect this, so LIMIT is still hack


> You could probably reach the same result with a subselect:
> select count(*) FROM (select body from txt where fts_index @@
> to_tsquery('oil') limit 1000)
>

yes, timings now are equal !

>
> At least that's how I think LIMIT works. That would certainly explain
> the major time difference.
>
> //Magnus
>

	Regards,
		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83



view thread (3+ messages)

Message-ID: <Pine.GSO.4.58.0410040049020.14217@ra.sai.msu.su>
Permalink:  ../Pine.GSO.4.58.0410040049020.14217@ra.sai.msu.su/
Also on:    postgresql.org/message-id/Pine.GSO.4.58.0410040049020.14217@ra.sai.msu.su

 · 

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-admin@postgresql.org
  Cc: oleg@sai.msu.su, mha@sollentuna.net, kris@musicrebellion.com, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] slow count() was: tsearch2 poor performance
  In-Reply-To: <Pine.GSO.4.58.0410040049020.14217@ra.sai.msu.su>
  References: <6BCB9D8A16AC4241919521715F4D8BCE475DE4@algol.sollentuna.se> <Pine.GSO.4.58.0410040049020.14217@ra.sai.msu.su>

* 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