pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: David Siebert <david@eclipsecat.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Yet another indexing issue.
Date: Tue, 19 Mar 2002 16:01:28 -0800 (PST)
Message-ID: <20020319155803.G37657-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <OJEIJALIHAIBMMBFLCOBOEOCEDAA.david@eclipsecat.com>

On Tue, 19 Mar 2002, David Siebert wrote:

> Here is the explain output
>
> Sort  (cost=293.24..293.24 rows=1 width=128)
>   ->  Seq Scan on phonecalls  (cost=0.00..293.23 rows=1 width=128)
>
> Here is the Table
> CREATE TABLE "phonecalls" (
>   "irecnum" int4 DEFAULT nextval('"phonecalls_irecnum_seq"'::text) NOT NULL,
>   "scaller" varchar(80),
>   "sphone" varchar(40),
>   "sphone2" varchar(40),
>   "squedby" varchar(40),
>   "sfor" varchar(40),
>   "dplaceddate" timestamp,
>   "dtakendate" timestamp,
>   "dresdate" timestamp,
>   "ipri" int4,
>   "istatus" int4,
>   "iresolution" int4,
>   "ireques" int4,
>   "snotes" varchar(3999),
>   "stakenby" varchar(40),
>   CONSTRAINT "phonecalls_irecnum_key" UNIQUE ("irecnum")
> );
>

> Where would one find set enable_seqscan=off; in the docs?

To be honest I'm not sure where it's mentioned.  It's a big tool that
lets you make some gross changes to the optimizer's planning (sets the
cost of sequence scan very very high).

Does doing it before the explain change the output?

Also, does making an index on phonecalls(istatus, sfor) [rather than
sfor,istatus] change the choice?




view thread (6+ messages)  latest in thread

Message-ID: <20020319155803.G37657-100000@megazone23.bigpanda.com>
Permalink:  ../20020319155803.G37657-100000@megazone23.bigpanda.com/
Also on:    postgresql.org/message-id/20020319155803.G37657-100000@megazone23.bigpanda.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: sszabo@megazone23.bigpanda.com, david@eclipsecat.com, pgsql-general@postgresql.org
  Subject: Re: Yet another indexing issue.
  In-Reply-To: <20020319155803.G37657-100000@megazone23.bigpanda.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