From: Josh Berkus <josh@agliodbs.com>
To: Girish Bajaj <gbajaj@tietronix.com>
To: pgsql-sql@postgresql.org
Subject: Re: Table Partitioning and Rules
Date: Thu, 17 Jul 2003 12:38:42 -0700
Message-ID: <200307171238.42550.josh@agliodbs.com> (raw)
In-Reply-To: <003b01c34c98$ca9861f0$7764a8c0@tietronix.com>
References: <003b01c34c98$ca9861f0$7764a8c0@tietronix.com>
Girish,
> I cant possibly index all the cols in the table.
Why not?
Seriously, what you can do is use query logging to log the columns and
combinations of columns that users most frequently ask for. Then you can
index for those queries.
Your partitioning scheme assumes that users will be searching on the last name
most of the time, so I'd start with that.
> Im getting a little confused here cause eventually I would want to join in
> this 250 million gigantic table as well.. and that would be a real big
> problem causing loads of sequential scans wouldn't it?
Yes, it would.
--
-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-sql@postgresql.org
Cc: josh@agliodbs.com, gbajaj@tietronix.com
Subject: Re: Table Partitioning and Rules
In-Reply-To: <200307171238.42550.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