| From: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
|---|---|
| To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
| Cc: | William Temperley <willtemperley(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Very large tables |
| Date: | 2008-11-28 19:43:31 |
| Message-ID: | 493049E3.6060106@cheapcomplexdevices.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Grzegorz Jaśkiewicz wrote:
>
> true, if you don't want to search on values too much ,or at all - use
> float[]. But otherwise, keep stuff in a tables as such.
> It might be humongous in size, but at the end of the day - prime thing
> when designing a db is speed of queries.
If he's worried about speed, he might look into porting contrib/intarray
to arrays of floats. I've had good luck improving performance by
converting big tables of ints into intarray with indexes.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2008-11-28 19:55:22 | why hash on the primary key? |
| Previous Message | William Temperley | 2008-11-28 18:46:54 | Re: Very large tables |