From: Marinos Yannikos <mjy@geizhals.at>
To: pgsql-sql@postgresql.org
Subject: Odd error message (" hash indexes do not support whole-index scans")
Date: Wed, 20 Apr 2005 17:23:06 +0200
Message-ID: <426673DA.2020203@geizhals.at> (raw)
Shouldn't PostgreSQL behave in a different way in this case? (e.g. just
not use the index):
Table "public.forum_messages"
message_id | integer | not null default
nextval('forum_messages_message_id_seq'::text)
parent_userid | integer |
supersededby | integer | default 0
"forum_messages_pkey" primary key, btree (message_id)
"idx_supersede" hash (supersededby) WHERE (supersededby > 0)
# select m1.message_id,m2.message_id,m1.parent_userid,m2.parent_userid
from forum_messages m1, forum_messages m2 where
m2.supersededby=m1.message_id and m2.supersededby>0;
ERROR: hash indexes do not support whole-index scans
Regards,
Marinos
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mjy@geizhals.at
Subject: Re: Odd error message (" hash indexes do not support whole-index scans")
In-Reply-To: <426673DA.2020203@geizhals.at>
* 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