database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-02 09:02:37 +03:00
Code Activity

Add C comment that we will have to remove an exclusion constraint check

Browse Source 
if we ever implement '<>' index opclasses.

Jeff Davis
This commit is contained in:
Bruce Momjian
2010-05-29 02:32:08 +00:00
parent 47d6d4485b
commit 7190220555
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/executor/execUtils.c
View File

@ -8,7 +8,7 @@
* *
* *
* IDENTIFICATION * IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/executor/execUtils.c,v 1.171 2010/02/26 02:00:41 momjian Exp $ * $PostgreSQL: pgsql/src/backend/executor/execUtils.c,v 1.172 2010/05/29 02:32:08 momjian Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
@ -1310,7 +1310,8 @@ retry:
/* /*
* We should have found our tuple in the index, unless we exited the loop * We should have found our tuple in the index, unless we exited the loop
* early because of conflict. Complain if not. * early because of conflict. Complain if not. If we ever implement
* '<>' index opclasses, this check will fail and will have to be removed.
*/ */
if (!found_self && !conflict) if (!found_self && !conflict)
ereport(ERROR, ereport(ERROR,