Re: pgsql: If an index depends on no columns of its table, give it a

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: If an index depends on no columns of its table, give it a
Date: 2007-11-09 09:21:53
Message-ID: 1194600113.4251.368.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Fri, 2007-11-09 at 04:05 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > I had understood the discussion to conclude that indexes that do not
> > depend on any column of the table to not be allowed at all.
>
> That was my first reaction too, but the point about unique-index behavior
> refutes it. Constraining a table to have at most one row is useful.

Sure is, and I've done it just a few days ago.

This SQL does it using standard syntax:

create table foo (handle integer primary key check (handle = 1));

It's also a lot more obvious than creating an index on a constant, which
seems like a wrinkle that we should disallow. It just sounds to me like
something that will break again in the future, so I'd rather disallow it
now rather than here "but we need to support zero column indexes too".

--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2007-11-09 15:52:52 pgsql: Allow XML processing instructions starting with "xml" while
Previous Message Simon Riggs 2007-11-09 09:16:54 Re: Fix for stop words in thesaurus file