| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Girish Bajaj" <gbajaj(at)tietronix(dot)com>, <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Table Partitioning and Rules |
| Date: | 2003-07-17 19:38:42 |
| Message-ID: | 200307171238.42550.josh@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2003-07-17 19:39:51 | Re: Table Partitioning and Rules |
| Previous Message | Tom Lane | 2003-07-17 19:24:59 | Re: OR vs UNION |