| From: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Advice for index design |
| Date: | 2013-04-12 13:29:39 |
| Message-ID: | kk9283$ctu$1@gonzo.reversiblemaps.ath.cx |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On 2013-04-10, JORGE MALDONADO <jorgemal1960(at)gmail(dot)com> wrote:
> Our application offers a catalog of artists where a user can select a range
> of birthdays and/or sex. For example, a user can get an artists catalog for
> those male artists who were born between May 1, 1970 and May 1, 1990
> ordered by birthday and, within each birthday date, ordered by name. I can
> think of defining one index for birthday, one index for name, and one index
> for sex. Also, I can think of defining a compound index for birthday +
> name. Also there could be a compound index for sex + name. Another option
> could be a compound index for birthday + sex + name. There are many
> possible combinations. What is a good index design approach?
the best approach depends on where you need the most improvement.
For your example query an undex on (sex,birthday,name) would be best.
--
⚂⚃ 100% natural
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jasen Betts | 2013-04-12 13:53:19 | Re: Restrict FOREIGN KEY to a part of the referenced table |
| Previous Message | Greg Sabino Mullane | 2013-04-11 23:36:45 | Re: Advice for index design |