Skip site navigation (1) Skip section navigation (2)

Re: WIP: generalized index constraints

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: generalized index constraints
Date: 2009-08-20 17:14:08
Message-ID: 4A8D8460.9070201@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Jeff Davis wrote:
> On Thu, 2009-08-20 at 11:47 +0300, Heikki Linnakangas wrote:
>> That sounds like the constraint is based on an existing index, but there
>> can't be any existing indexes on a table that hasn't been created yet.
>> If this creates the index, then the syntax needs to support specifying
>> index access method and an opclass for all the columns.
> 
> Of course, thanks for pointing that out. To make it work at CREATE TABLE
> time, the language would have to specify the index access method, and
> the index name should be optional. Do you think it's worthwhile adjust
> the syntax for that, or would it just bloat the CREATE TABLE syntax for
> no reason?
> 
> I'm leaning toward not allowing it at CREATE TABLE time.

Seems reasonable to me too.

> However, I'm not sure if it's very easy to provide support for
> concurrent index building. Should I block it, or is it worth
> investigating further?

Dunno. It sure would be nice, but it's not a showstopper.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2009-08-20 17:28:32
Subject: Re: Multi-pass planner
Previous:From: Robert HaasDate: 2009-08-20 17:10:15
Subject: Re: Multi-pass planner

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group