pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andreas Pflug <Andreas.Pflug@web.de>
To: pgsql-performance@postgresql.org
Subject: Re: Slow query performance on large table
Date: Tue, 04 Mar 2003 22:45:36 +0100
Message-ID: <3E651E80.9070807@web.de> (raw)
In-Reply-To: <3E64E079.8050807@klaster.net>
References: <000001c2e25c$ad506170$0c64a8c0@paulspc>
	<23081.1046790781@sss.pgh.pa.us>
	<3E64D694.9050309@web.de>
	<3E64E079.8050807@klaster.net>

Tomasz Myrta wrote:

> You are right - primary key should be ok, but Paul lost it. psql \d 
> shows primary key indexes, but in this case there was no such primary 
> key.
>
> Regards,
> Tomasz Myrta
>
Ok,

then my view of the world is all right again.

Re Tom Lane

> One would like to think the optimizer will make the right choice.  But
> using a two-column index just because it's there isn't necessarily the
> right choice.  The two-column index will certainly be bulkier and more
> expensive to scan, so if there's a one-column index that's nearly as
> selective, it might be a better choice.


If I know that the access pattern of my app looks as if it will need a 
multipart index I should create it. If the optimizer finds out, a 
simpler one will fit better, all right, it knows better (if properly 
VACUUMed :-). But it's still good practice to offer complete indices. 
Will pgsql use a multipart index as efficiently for simpler queries as a 
shorter one covering only the first columns? In this example, the 
(assessment, time) index could replace the (accessment) index, but 
certainly not the (time) index. I tend to design longer indices with 
hopefully valuable columns.

In this context:
 From MSSQL, I know "covering indices". Imagine a table t with many 
columns, and an index on (a,b,c).
in MSSQL, SELECT c from t where (a ... AND b...) will use that index to 
retrieve the c column value also without touching the row data. In a 
sense, the index is used as an alternative table. Does pgsql profit from 
this kind of indices also?

Regards,

Andreas




view thread (18+ messages)  latest in thread

Message-ID: <3E651E80.9070807@web.de>
Permalink:  ../3E651E80.9070807@web.de/
Also on:    postgresql.org/message-id/3E651E80.9070807@web.de

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: Andreas.Pflug@web.de
  Subject: Re: Slow query performance on large table
  In-Reply-To: <3E651E80.9070807@web.de>
  References: <000001c2e25c$ad506170$0c64a8c0@paulspc> <23081.1046790781@sss.pgh.pa.us> <3E64D694.9050309@web.de> <3E64E079.8050807@klaster.net> <3E651E80.9070807@web.de>

* 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