pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Two Index Questions
Date: Fri, 19 Jul 2002 12:44:07 -0400
Message-ID: <13606.1027097047@sss.pgh.pa.us> (raw)
In-Reply-To: <200207190933.59283.josh@agliodbs.com>
References: <200207190933.59283.josh@agliodbs.com>

Josh Berkus <josh@agliodbs.com> writes:
> Q:  If you group a table by multiple colums, e.g.
> 	SELECT t1.A, t1.B, t1.C, MAX(t1.G)
> 	FROM t1
> 	GROUP BY t1.A, t1.B, t1.C
>   Then would a multi-column index on A, B, C be faster than seperate indexes 
> on A, B and C?

An indexscan can only use one index, so separate indexes would be
completely worthless for this query.  An index on A,B,C is potentially
useful, but in most cases I think the planner will prefer an explicit
sort anyway if there's no WHERE clause.

> Q: In PostgreSQL 7.0, there was an issue that indexes where never consulted 
> for DESC alpha sorts.   Has this been resolved?  If so, does one need to 
> create any special indexes to take advantage of indexes for DESC sorts?

Yes; no.

regression=# create table foo (f1 text);
CREATE TABLE
regression=# create index fooi on foo(f1);
CREATE INDEX
regression=# explain select * from foo order by f1;
                             QUERY PLAN
---------------------------------------------------------------------
 Index Scan using fooi on foo  (cost=0.00..52.00 rows=1000 width=32)
(1 row)

regression=# explain select * from foo order by f1 desc;
                                  QUERY PLAN
------------------------------------------------------------------------------
 Index Scan Backward using fooi on foo  (cost=0.00..52.00 rows=1000 width=32)
(1 row)


			regards, tom lane



view thread (10+ messages)  latest in thread

Message-ID: <13606.1027097047@sss.pgh.pa.us>
Permalink:  ../13606.1027097047@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13606.1027097047@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
  Subject: Re: Two Index Questions
  In-Reply-To: <13606.1027097047@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox