From: John Beaver <john.e.beaver@gmail.com>
To: pgsql-performance@postgresql.org
Subject: large tables and simple "= constant" queries using indexes
Date: Wed, 09 Apr 2008 16:58:27 -0400
Message-ID: <47FD2DF3.80500@gmail.com> (raw)
Hi, I've started my first project with Postgres (after several years of
using Mysql), and I'm having an odd performance problem that I was
hoping someone might be able to explain the cause of.
----My query----
- select count(*) from gene_prediction_view where gene_ref = 523
- takes 26 seconds to execute, and returns 2400 (out of a total of
15 million records in the table)
---My problem---
Using a single-column index to count 2400 records which are exactly
one constant value doesn't sound like something that would take 26
seconds. What's the slowdown? Any silver bullets that might fix this?
----Steps I've taken----
- I ran vacuum and analyze
- I upped the shared_buffers to 58384, and I upped some of the other
postgresql.conf values as well. Nothing seemed to help significantly,
but maybe I missed something that would help specifically for this query
type?
- I tried to create a hash index, but gave up after more than 4
hours of waiting for it to finish indexing
----Table stats----
- 15 million rows; I'm expecting to have four or five times this
number eventually.
- 1.5 gigs of hard drive usage
----My development environment---
- 2.6ghz dual-core MacBook Pro with 4 gigs of ram and a 7200 rpm
hard drive
- OS X 10.5.2
- Postgres 8.3 (installed via MacPorts)
----My table----
CREATE TABLE gene_prediction_view
(
id serial NOT NULL,
gene_ref integer NOT NULL,
go_id integer NOT NULL,
go_description character varying(200) NOT NULL,
go_category character varying(50) NOT NULL,
function_verified_exactly boolean NOT NULL,
function_verified_with_parent_go boolean NOT NULL,
function_verified_with_child_go boolean NOT NULL,
score numeric(10,2) NOT NULL,
precision_score numeric(10,2) NOT NULL,
CONSTRAINT gene_prediction_view_pkey PRIMARY KEY (id),
CONSTRAINT gene_prediction_view_gene_ref_fkey FOREIGN KEY (gene_ref)
REFERENCES sgd_annotations (id) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT gene_prediction_view_go_id_fkey FOREIGN KEY (go_id)
REFERENCES go_terms (term) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT gene_prediction_view_gene_ref_key UNIQUE (gene_ref, go_id)
)
WITH (OIDS=FALSE);
ALTER TABLE gene_prediction_view OWNER TO postgres;
CREATE INDEX ix_gene_prediction_view_gene_ref
ON gene_prediction_view
USING btree
(gene_ref);
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-performance@postgresql.org
Cc: john.e.beaver@gmail.com
Subject: Re: large tables and simple "= constant" queries using indexes
In-Reply-To: <47FD2DF3.80500@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