| From: | "Pierre C" <lists(at)peufeu(dot)com> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
| Cc: | dba <dbadbb(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: performance issue in the fields. |
| Date: | 2011-02-24 08:22:53 |
| Message-ID: | op.vreewfeleorkce@apollo13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>>> I have created two tables. In the first table i am using many fields to
>>> store 3 address.
>>> as well as in b table, i am using array data type to store 3 address.
>>> is
>>> there any issue would face in performance related things.... which one
>>> will
>>> cause the performance issue.
The array is interesting :
- if you put a gist index on it and do searches like "array contains
values X and Y and Z", gist index has a some special optimizations for this
- if you might store a variable number of integers, and for some reason
you don't want a normalized one-line-per-value approach
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mathieu De Zutter | 2011-02-24 09:47:07 | Re: NULLS LAST performance |
| Previous Message | Dave Johansen | 2011-02-24 04:10:31 | Pushing IN (subquery) down through UNION ALL? |