X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 363F3474E5C for ; Mon, 10 Feb 2003 05:25:11 -0500 (EST) Received: from klingon.netkonect.net (klingon.netkonect.co.uk [194.62.44.61]) by postgresql.org (Postfix) with ESMTP id 0E409474E53 for ; Mon, 10 Feb 2003 05:25:09 -0500 (EST) Received: from cheetah.webtribe.net (cheetah.webtribe.net [194.164.194.4]) by klingon.netkonect.net (8.11.4/8.11.4) with ESMTP id h1AAP8N01367 for ; Mon, 10 Feb 2003 10:25:08 GMT Received: from localhost (cheetah.webtribe.net [194.164.194.4]) by cheetah.webtribe.net (Postfix) with SMTP id 84E5D18332 for ; Mon, 10 Feb 2003 10:25:07 +0000 (GMT) Cc: Subject: index strategies Content-type: text/plain X-mailer: WebMail Date: Mon, 10 Feb 2003 10:25 +0000 Mime-version: 1.0 To: pgsql-sql@postgresql.org From: val@webtribe.net Message-Id: <20030210102507.84E5D18332@cheetah.webtribe.net> Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/189 X-Sequence-Number: 11587 Can someone point me in the direction of some good, useful info=20 re: datamine index strategies? I have one BIG table (apr : Attribute | Type | Modifier -----------+--------------------------+---------- dnis | text | cli | text | iplogin | text | brand | text | begintime | timestamp with time zone | endtime | timestamp with time zone | ipaddr | text Any one of the columns may be used in the where clause of a=20 select statement.=20=20 There are also aggregates used in select statements (e.g., sum(endtime-begintime) group by iplogin AND count(*)=20 group by iplogin). I have a small clue (ha!) about indexing but want to know the=20 proper way to attack the indexing strategy. Any info given is v much appreciated. Val