Re: SELECT results in "ERROR: index key does not match expected index column" - Mailing list pgsql-bugs

From Andrew Gierth
Subject Re: SELECT results in "ERROR: index key does not match expected index column"
Date
Msg-id 87tvc3q1ob.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: SELECT results in "ERROR: index key does not match expected index column"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SELECT results in "ERROR: index key does not match expected index column"  (Manuel Rigger <rigger.manuel@gmail.com>)
List pgsql-bugs
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:

 Tom> (You realize of course that an index on a constant is pretty
 Tom> useless. I wonder if we should disallow that.)

Unique index on a constant is a standard technique for forcing a table
to be limited to at most one row (or with a partial index, at most one
row matching a condition). Non-unique index on a constant is probably
not useful though.

-- 
Andrew (irc:RhodiumToad)



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: SELECT results in "ERROR: index key does not match expected index column"
Next
From: PG Bug reporting form
Date:
Subject: BUG #15887: An extra "break" instruction causes a bug