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

help / color / mirror / Atom feed
From: Nikolay Samokhvalov <samokhvalov@gmail.com>
To: pgsql-sql@postgresql.org, "Bryce Nesbitt" <bryce1@obviously.com>
Subject: Re: Sequential scan where Index scan expected.
Date: Sat, 4 Mar 2006 22:07:20 +0300
Message-ID: <e431ff4c0603041107h489626b7r32840cc5d2bc9499@mail.gmail.com> (raw)
In-Reply-To: <4407EFD9.7050008@obviously.com>
References: <244004377.20060302124132@isb.com.pl>
	<2873.1141312882@sss.pgh.pa.us>
	<4407EFD9.7050008@obviously.com>

please, show '\d xx_thing_event' too :-)

On 3/3/06, Bryce Nesbitt <bryce1@obviously.com> wrote:
> I'm getting sequential scans (and poor performance), on scans using my
> primary keys.
> 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)
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>


--
Best regards,
Nikolay


view thread (9+ messages)

Message-ID: <e431ff4c0603041107h489626b7r32840cc5d2bc9499@mail.gmail.com>
Permalink:  ../e431ff4c0603041107h489626b7r32840cc5d2bc9499@mail.gmail.com/
Also on:    postgresql.org/message-id/e431ff4c0603041107h489626b7r32840cc5d2bc9499@mail.gmail.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: samokhvalov@gmail.com, bryce1@obviously.com
  Subject: Re: Sequential scan where Index scan expected.
  In-Reply-To: <e431ff4c0603041107h489626b7r32840cc5d2bc9499@mail.gmail.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