From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
---|---|
To: | Morris de Oryx <morrisdeoryx(at)gmail(dot)com>, Jeremy Finzel <finzelj(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Questions about btree_gin vs btree_gist for low cardinality columns |
Date: | 2019-06-01 08:24:00 |
Message-ID: | 45a5915b-870b-1dea-ca1d-395b067940ad@archidevsys.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 01/06/2019 14:52, Morris de Oryx wrote:
[...]
> For an example, imagine an address table with 100M US street addresses
> with two character state abbreviations. So, say there are around 60
> values in there (the USPS is the mail system for a variety of US
> territories, possessions and friends in the Pacific.) Okay, so what's
> the best index type for state abbreviation? For the sake of argument,
> assume a normal distribution so something like FM (Federated States of
> Micronesia) is on a tail end and CA or NY are a whole lot more common.
[...]
I'd expect the distribution of values to be closer to a power law than
the Normal distribution -- at very least a few states would have the
most lookups. But this is my gut feel, not based on any scientific
analysis!
Cheers,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Morris de Oryx | 2019-06-01 09:02:56 | Re: Questions about btree_gin vs btree_gist for low cardinality columns |
Previous Message | Morris de Oryx | 2019-06-01 07:44:00 | Re: Questions about btree_gin vs btree_gist for low cardinality columns |