From: Jeff Boes <jboes@nexcerpt.com>
To: pgsql-performance@postgresql.org
Subject: Optimizer differences between 7.2 and 7.3
Date: 07 Jul 2003 10:17:35 -0400
Message-ID: <1057587455.6466.26.camel@takin.private.nexcerpt.com> (raw)
Our production database is running under 7.2.4; our test database
running almost the same data is at 7.3.3. One table has about 400,000
rows in each schema. A query against an indexed column uses an index
scan under 7.2.4, but a sequential scan under 7.3.3. A count of the
table in question shows that they have comparable numbers of matching
rows.
On 7.2.4:
select count(*) from articles;
count
--------
420213
select count(*) from articles
where path_base like 'http://news.findlaw.com/hdocs%';;
count
-------
38
(and it returns this nearly instantaneously)
explain select count(*) from articles
where path_base like 'http://news.findlaw.com/hdocs%';
Aggregate (cost=6.02..6.02 rows=1 width=0)
-> Index Scan using ix_articles_3 on articles (cost=0.00..6.01
rows=1 width=0)
On 7.3.3:
select count(*) from articles;
count
--------
406319
select count(*) from articles
where path_base like 'http://news.findlaw.com/hdocs%';
count
-------
23
(and it takes many seconds to return)
explain select count(*) from articles
where path_base like 'http://news.findlaw.com/hdocs%';
Aggregate (cost=205946.65..205946.65 rows=1 width=0)
-> Seq Scan on articles (cost=0.00..205946.65 rows=1 width=0)
Filter: (path_base ~~ 'http://news.findlaw.com/hdocs%'::text)
I can't find any differences between the indexes (ix_articles_3 exists
in both schemas); the column statistics are set up the same (the
default); and the optimizer settings (costs in postgresql.conf) are the
same.
--
Jeff Boes vox 269.226.9550 ext 24
Database Engineer fax 269.349.9076
Nexcerpt, Inc. http://www.nexcerpt.com
...Nexcerpt... Extend your Expertise
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-performance@postgresql.org
Cc: jboes@nexcerpt.com
Subject: Re: Optimizer differences between 7.2 and 7.3
In-Reply-To: <1057587455.6466.26.camel@takin.private.nexcerpt.com>
References: <1057587455.6466.26.camel@takin.private.nexcerpt.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