| From: | Ravi Krishna <srkrishna1(at)aol(dot)com> |
|---|---|
| To: | |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | GIN Index for low cardinality |
| Date: | 2018-10-17 10:46:36 |
| Message-ID: | E260AEE7-95B3-4142-9A4B-A4416F1701F0@aol.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In https://www.cybertec-postgresql.com/en/ideas-for-scaling-postgresql-to-multi-terabyte-and-beyond/
it is mentioned:
"GIN, the most know non-default index type perhaps, has been actually around for ages (full-text search) and in short is perfect for indexing columns where there are lot of repeating values – think all kinds of statuses or good old Mr/Mrs/Miss. GIN only stores every unique column value only once as for the default B-tree you’ll have e.g. 1 millon leaf nodes with the integer “1” in it."
Does it mean that GIN is a very good choice for low cardinality columns.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-10-17 12:13:33 | Re: BUG: Incorrect working with POSIX locale if database in UTF-8 encoding |
| Previous Message | Олег Самойлов | 2018-10-17 09:29:52 | BUG: Incorrect working with POSIX locale if database in UTF-8 encoding |