From: AJ Weber <aweber@comcast.net>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: how to improve perf of 131MM row table?
Date: Wed, 25 Jun 2014 16:10:25 -0400
Message-ID: <53AB2CB1.8080201@comcast.net> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Sorry for the semi-newbie question...
I have a relatively sizable postgresql 9.0.2 DB with a few large tables
(keep in mind "large" is relative, I'm sure there are plenty larger out
there).
One of my queries that seems to be bogging-down performance is a join
between two tables on each of their BIGINT PK's (so they have default
unique constraint/PK indexes on them). One table is a detail table for
the other. The "master" has about 6mm rows. The detail table has about
131mm rows (table size = 17GB, index size = 16GB).
I unfortunately have limited disks, so I can't actually move to multiple
spindles, but wonder if there is anything I can do (should I partition
the data, etc.) to improve performance? Maybe some further tuning to my
.conf, but I do think that's using as much mem as I can spare right now
(happy to send it along if it would help).
DB is vacuumed nightly with stats updates enabled. I can send the
statistics info listed in pgAdmin tab if that would help.
Any suggestions, tips, tricks, links, etc. are welcomed!
Thanks in advance,
AJ
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: aweber@comcast.net
Subject: Re: how to improve perf of 131MM row table?
In-Reply-To: <53AB2CB1.8080201@comcast.net>
* 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