From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Ken Egervari <ken@upfactor.com>
Subject: Re: Performance problem with semi-large tables
Date: Sat, 29 Jan 2005 13:51:10 -0800
Message-ID: <200501291351.10335.josh@agliodbs.com> (raw)
In-Reply-To: <001601c50416$57090e10$cd422418@a96dfxb4kjzogw>
References: <001601c50416$57090e10$cd422418@a96dfxb4kjzogw>
Ken,
Actually, your problem isn't that generic, and might be better solved by
dissecting an EXPLAIN ANALYZE.
> 1. Should I just change beg to change the requirements so that I can make
> more specific queries and more screens to access those?
This is always good.
> 2. Can you
> recommend ways so that postgres acts on big tables more efficiently? I'm
> not really interested in this specific case (I just made it up). I'm more
> interested in general solutions to this general problem of big table sizes
> with bad filters and where join orders don't seem to help much.
Well, you appear to be using ORDER BY ... LIMIT. Is there a corresponding
index on the order by criteria?
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, ken@upfactor.com
Subject: Re: Performance problem with semi-large tables
In-Reply-To: <200501291351.10335.josh@agliodbs.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