pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Bryce Nesbitt <bryce1@obviously.com>
To: pgsql-sql@postgresql.org
Subject: Sequential scan where Index scan expected (update)
Date: Thu, 02 Mar 2006 23:28:49 -0800
Message-ID: <4407F031.6050706@obviously.com> (raw)
In-Reply-To: <2873.1141312882@sss.pgh.pa.us>
References: <244004377.20060302124132@isb.com.pl>
	<2873.1141312882@sss.pgh.pa.us>

I'm getting sequential scans (and poor performance), on scans using my
primary keys.  This is an older postgres.
Can anyone help figure out why?


demo=# \d xx_thing
                     Table "public.xx_thing"
         Column          |            Type             | Modifiers
-------------------------+-----------------------------+-----------
 thing_id              | bigint                      | not null
thing_model           | character varying(128)      |
 thing_color           | character varying(128)      |
 thing_year            | integer                     |
Indexes:
    "xx_thing_pkey" primary key, btree (thing_id)


demo=# analyze verbose xx_thing_event;
INFO:  analyzing "public.xx_thing_event"
INFO:  "xx_thing_event": 3374 pages, 3000 rows sampled, 197478 estimated
total rows


demo=# explain update xx_thing_event set thing_color='foo' where
thing_event_id=10000;
                             QUERY PLAN
---------------------------------------------------------------------
 Seq Scan on xx_thing_event  (cost=0.00..5842.48 rows=1 width=110)
   Filter: (thing_event_id = 10000)
(2 rows)



demo=# select * from version();
                                                 version
----------------------------------------------------------------------------------------------------------
 PostgreSQL 7.4.1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.3
20030502 (Red Hat Linux 3.2.3-20)
(1 row)




view thread (9+ messages)  latest in thread

Message-ID: <4407F031.6050706@obviously.com>
Permalink:  ../4407F031.6050706@obviously.com/
Also on:    postgresql.org/message-id/4407F031.6050706@obviously.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: bryce1@obviously.com
  Subject: Re: Sequential scan where Index scan expected (update)
  In-Reply-To: <4407F031.6050706@obviously.com>

* 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