allow-exclude-ne.patch
text/x-patch
Filename: allow-exclude-ne.patch
Type: text/x-patch
Part: 0
Message:
small exclusion constraints patch
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: context
| File | + | − |
|---|---|---|
| src/backend/executor/execUtils.c | 5 | 0 |
*** a/src/backend/executor/execUtils.c
--- b/src/backend/executor/execUtils.c
***************
*** 1309,1323 **** retry:
index_endscan(index_scan);
/*
! * We should have found our tuple in the index, unless we exited the loop
! * early because of conflict. Complain if not.
*/
- if (!found_self && !conflict)
- ereport(ERROR,
- (errcode(ERRCODE_INTERNAL_ERROR),
- errmsg("failed to re-find tuple within index \"%s\"",
- RelationGetRelationName(index)),
- errhint("This may be because of a non-immutable index expression.")));
econtext->ecxt_scantuple = save_scantuple;
--- 1309,1320 ----
index_endscan(index_scan);
/*
! * Ordinarily, at this point the search should have found the
! * inserted tuple if there was no conflict. However, there are
! * some cases where a tuple may not conflict with itself, and
! * therefore would _not_ have found itself in this search -- for
! * instance, if the operator is <>.
*/
econtext->ecxt_scantuple = save_scantuple;