| From: | "Sergei Shelukhin" <realgeek(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: one more performance question I cannot test yet :( |
| Date: | 2007-04-14 20:56:37 |
| Message-ID: | 1176584197.006557.225330@b75g2000hsg.googlegroups.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Apr 15, 12:13 am, "Sergei Shelukhin" <realg(dot)(dot)(dot)(at)gmail(dot)com> wrote:
> Suppose there's a table with two text fields and a lot of int fields.
> THe table will be huge, updated constantly, and will be searched by
> all of the int fields, whereas text fields will be for display only.
>
> Does it make sense to split it vertically into two tables, one with
> ints and one with texts, and join them in queries to make it faster?
Also, with a limited test data I have, I tried running queries against
two table scheme...
ifyou join two tables by id = id ( both ids are primary keys) it uses
hash join, however as soon as you add a condition on one of the
columns in ints' table, it degrades to nested loop. Wtf? Is there any
way to force it to used clustered indexes for gods sake?!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-14 22:09:18 | Re: Help setting up warm standby replication |
| Previous Message | Sergei Shelukhin | 2007-04-14 20:13:44 | one more performance question I cannot test yet :( |