| From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Advice for index design |
| Date: | 2013-04-11 23:36:45 |
| Message-ID: | ce7aaa1fa52475c028836bf3e31473d4@biglumber.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Jorge Maldonado wrote:
...
> What is a good index design approach? Maybe, setting simple separate
> indexes (one for each field) would work fine if I need to
> retrieve data in different combinatios, but I am not sure.
Yes, just create separate indexes and you will be fine, especially given
the very small size of the table. If you find your queries going slow, you
could start investigating compound indexes (or in this case, partial
indexes).
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201304111933
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAlFnSPYACgkQvJuQZxSWSshm6wCggdl2FyowAbca93hYKXGgcXoE
iN0AniOL8OS3teTgk6thxkJjUGqEf15k
=1Eb6
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jasen Betts | 2013-04-12 13:29:39 | Re: Advice for index design |
| Previous Message | androclos | 2013-04-11 16:38:39 | Slow update with ST_Contians() |