pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <e99re41@DoCS.UU.SE>
To: David Celjuska <dcsoft@dcsoft.sk>
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] database with 1000000 rows is very slow
Date: Mon, 6 Mar 2000 08:22:05 +0100 (MET)
Message-ID: <Pine.GSO.4.02A.10003060817320.17581-100000@Svan.DoCS.UU.SE> (raw)
In-Reply-To: <38C2C1E1.A41501BD@dcsoft.sk>

On Sun, 5 Mar 2000, David Celjuska wrote:

> CREATE UNIQUE INDEX "article_pkey" on "article" using btree ( "id"
> "varchar_ops" );

> this database store. But I think that select * from article where id
> like 'something%' is very slow (some minutes) and query as: select *
> from article where id='something' is very slow too. I don't know where
> is a problem a I would like optimalise this, but how can I do it?

If you haven't run vacuum analyze lately then you should do that.

> When I use hash except btree, query as: select * from article where
> id='something' is fast but select * from article where id='something%'
> is very slow.

Yup. That's because hashes only work on exact matches and btrees can do
ordering (like 'somethink' is surely "larger" than 'something%').

> Or postgresql make indexes automaticly?

No, you have to make them, but you did that right.

> How can I see that postgres use/or no use index on some query? It is
> possible?

Yup. EXPLAIN SELECT ....

In fact, if you can't make any progress you should always accompany any
optimizer issues with the EXPLAIN output. That will help our optimizer
gurus. :)


-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden




view thread (6+ messages)  latest in thread

Message-ID: <Pine.GSO.4.02A.10003060817320.17581-100000@Svan.DoCS.UU.SE>
Permalink:  ../Pine.GSO.4.02A.10003060817320.17581-100000@Svan.DoCS.UU.SE/
Also on:    postgresql.org/message-id/Pine.GSO.4.02A.10003060817320.17581-100000@Svan.DoCS.UU.SE

 · 

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-sql@postgresql.org
  Cc: e99re41@DoCS.UU.SE, dcsoft@dcsoft.sk
  Subject: Re: [SQL] database with 1000000 rows is very slow
  In-Reply-To: <Pine.GSO.4.02A.10003060817320.17581-100000@Svan.DoCS.UU.SE>
  References: <38C2C1E1.A41501BD@dcsoft.sk> <Pine.GSO.4.02A.10003060817320.17581-100000@Svan.DoCS.UU.SE>

* 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