Skip site navigation (1) Skip section navigation (2)

Re: optimizing Postgres queries

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: David Teran <david(dot)teran(at)cluster9(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: optimizing Postgres queries
Date: 2004-01-06 05:25:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
David Teran wrote:
> Index?Scan?using?key_value_meta_data__id_value__fk_index,?key_value_meta 
> _data__id_value__fk_index?on?"KEY_VALUE_META_DATA"?t0??(cost=0.00..19.94 
> ?rows=14?width=75)?(actual?time=0.112..0.296?rows=25?loops=1)
> ??Index?Cond:?(("ID_VALUE"?=?21094)?OR?("ID_VALUE"?=?21103))
> Total runtime: 0.429 ms
> Much better. So i think i will first read more about this optimization  
> stuff and regular maintenance things. This is something i like very  
> much from FrontBase: no need for such things, simply start and run. But  
> other things were not so fine ;-).
> Is there any hint where to start to understand more about this  
> optimization problem?

Read the FAQ.  There is an item about slow queries and indexes.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-performance by date

Next:From: Shridhar DaithankarDate: 2004-01-06 06:31:53
Subject: Re: Select max(foo) and select count(*) optimization
Previous:From: Christopher BrowneDate: 2004-01-06 02:31:29
Subject: Re: Select max(foo) and select count(*) optimization

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group