From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ingram, Bryan <BIngram@sixtyfootspider.com>
Cc: 'pgsql-sql@postgresql.org' <pgsql-sql@postgresql.org>
Subject: Re: Why is this doing a seq scan?
Date: Fri, 17 Nov 2000 15:06:13 -0500
Message-ID: <13934.974491573@sss.pgh.pa.us> (raw)
In-Reply-To: <01CCE949D2717845BA2E573DC081167E052FAE@BKMAIL.sfsinternal.com>
References: <01CCE949D2717845BA2E573DC081167E052FAE@BKMAIL.sfsinternal.com>
Hmm. Have you VACUUM ANALYZED the tables? If so, what do you get from
these queries:
select attname,attdisbursion,s.*
from pg_statistic s, pg_attribute a, pg_class c
where starelid = c.oid and attrelid = c.oid and staattnum = attnum
and relname = 'zips';
select attname,attdisbursion,s.*
from pg_statistic s, pg_attribute a, pg_class c
where starelid = c.oid and attrelid = c.oid and staattnum = attnum
and relname = 'atms';
Also it would be useful to see the full declarations of the tables
and their indexes; I'm wondering what datatype the zip columns are,
for example.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, BIngram@sixtyfootspider.com
Subject: Re: Why is this doing a seq scan?
In-Reply-To: <13934.974491573@sss.pgh.pa.us>
References: <01CCE949D2717845BA2E573DC081167E052FAE@BKMAIL.sfsinternal.com> <13934.974491573@sss.pgh.pa.us>
* 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