Return-Path: mao
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA17697; Tue, 1 Dec 92 09:57:48 -0800
Message-Id: <9212011757.AA17697@postgres.Berkeley.EDU>
From: <mao@postgres.berkeley.edu>
Subject: Re: DEFINE INDEX BUG?
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of Tue, 01 Dec 92 07:37:36 PST.
             <9212011537.AA16918@postgres.Berkeley.EDU> 
Date: Tue, 01 Dec 92 09:59:01 PST

In message <9212011537.AA16918@postgres.Berkeley.EDU> you write:

> What is implied here? I understand that keys are 
> not implemented in the current version of postgres(4.0.1).
> Anybody have any ideas what is meant by this
> bug listing?

primary keys are not supported.  'index key' refers to the attribute that's
used to control ordering in the index.  the bug is that you can define
an index on (emp.salary), but not on (emp.salary, emp.age), which would order
employees by salary, and within a single salary by age.

					mike