On 2013-04-10, JORGE MALDONADO <jorgemal1...@gmail.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 -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql