Re: poor performance involving a small table

From: andrew(at)pillette(dot)com
To: Colton A Smith <smith(at)cs(dot)utk(dot)edu>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: poor performance involving a small table
Date: 2005-05-31 02:31:06
Message-ID: 200505310231.j4V2V6e25466@pillette.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

This is a multi-part message in MIME format.

--bound1117506666
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Colton A Smith <smith(at)cs(dot)utk(dot)edu> wrote ..

------------------------------------------------------------------------------------------------
> Seq Scan on sensor (cost=0.00..1.25 rows=1 width=6) (actual
> time=0.055..0.068 rows=1 loops=1)
> Filter: (sensor_id = 12)
> Total runtime: 801641.333 ms
> (3 rows)

Do you have some foreign keys pointing in the other direction? In other words, is there another table such that a delete on sensors causing a delete (or a check of some key) in another table? EXPLAIN doesn't show these. And that might be a big table missing an index.

--bound1117506666--

Browse pgsql-performance by date

  From Date Subject
Next Message Tobias Brox 2005-05-31 03:02:07 Index on a NULL-value
Previous Message Tobias Brox 2005-05-31 02:20:11 Re: timestamp indexing