From: Dave Dutcher <dave@tridecap.com>
To: 'Glenn Sullivan' <glenn.sullivan@varianinc.com>
To: pgsql-performance@postgresql.org
Subject: Re: SELECT performance problem
Date: Tue, 20 Feb 2007 17:46:56 -0600
Message-ID: <002701c75549$680881b0$8300a8c0@tridecap.com> (raw)
In-Reply-To: <45DB8290.1020501@varianinc.com>
Did you run ANALYZE on your data after importing it into 8.2.3? Is there an
index on the seqfil column? If so, you should post the output of EXPLAIN
ANALYZE from both systems if possible.
> -----Original Message-----
> From: pgsql-performance-owner@postgresql.org
> [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of
> Glenn Sullivan
> Sent: Tuesday, February 20, 2007 5:22 PM
> To: pgsql-performance@postgresql.org
> Subject: [PERFORM] SELECT performance problem
>
>
> I am updating from 7.4.5 to 8.2.3. I have noticed a significant
> slowdown in simple searches such as
> "select filename from vnmr_data where seqfil = 'sems';"
> This returns 12 rows out of 1 million items in the table.
> On 7.4.5, this takes about 1.5 seconds. On 8.2.3, it is taking
> about 9 seconds.
>
> I have played with different values of:
> work_mem, temp_buffers, shared_buffers and effective_cache_size
> and none of them make any difference.
>
> I am running on redhat Linux 4 64bit.
>
> Any ideas?
>
> Glenn
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org
> so that your
> message can get through to the mailing list cleanly
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: dave@tridecap.com, glenn.sullivan@varianinc.com
Subject: Re: SELECT performance problem
In-Reply-To: <002701c75549$680881b0$8300a8c0@tridecap.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