| From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | Ozz Nixon <ozznixon(at)gmail(dot)com>, "jeff(dot)janes(at)gmail(dot)com" <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | "splarv(at)ya(dot)ru" <splarv(at)ya(dot)ru>, "srkrishna1(at)aol(dot)com" <srkrishna1(at)aol(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: GIN Index for low cardinality |
| Date: | 2018-10-26 17:21:49 |
| Message-ID: | DM5PR17MB153244B2A898D6FFABAE624EDAF00@DM5PR17MB1532.namprd17.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
From: Ozz Nixon <ozznixon(at)gmail(dot)com>
Sent: Friday, October 26, 2018 12:50 PM
To: jeff(dot)janes(at)gmail(dot)com
Cc: splarv(at)ya(dot)ru; srkrishna1(at)aol(dot)com; pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: GIN Index for low cardinality
Jeff,
Great info! Your example on Mr. Mrs. Miss, etc. is there a good rule of thumb that if the data is under "x"KB an index is overhead not help? I am not worried about space, more interested in performance.
I think, partial/conditional indexes: …. Where greeting = ‘…’ – may help.
Regards,
Igor Neyman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yuxia Qiu | 2018-10-26 17:37:59 | How to get partition info for a partition table? |
| Previous Message | Thomas Kellerer | 2018-10-26 17:10:34 | Re: Different memory allocation strategy in Postgres 11? |