diff options
| author | Tom Lane | 2011-10-23 04:43:39 +0000 |
|---|---|---|
| committer | Tom Lane | 2011-10-23 04:43:39 +0000 |
| commit | 0f39d5050dc0dce99258381f33f1832c437aff85 (patch) | |
| tree | 90583250bd5cf7878686bad038ec74e9dd292744 /src/include | |
| parent | bb446b689b6681eb57a8a50605e119743190c4db (diff) | |
Don't trust deferred-unique indexes for join removal.
The uniqueness condition might fail to hold intra-transaction, and assuming
it does can give incorrect query results. Per report from Marti Raudsepp,
though this is not his proposed patch.
Back-patch to 9.0, where both these features were introduced. In the
released branches, add the new IndexOptInfo field to the end of the struct,
to try to minimize ABI breakage for third-party code that may be examining
that struct.
Diffstat (limited to 'src/include')
| -rw-r--r-- | src/include/nodes/relation.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/include/nodes/relation.h b/src/include/nodes/relation.h index 2925d7e7659..ede97571e06 100644 --- a/src/include/nodes/relation.h +++ b/src/include/nodes/relation.h @@ -488,6 +488,7 @@ typedef struct IndexOptInfo bool predOK; /* true if predicate matches query */ bool unique; /* true if a unique index */ + bool immediate; /* is uniqueness enforced immediately? */ bool hypothetical; /* true if index doesn't really exist */ bool amcanorderbyop; /* does AM support order by operator result? */ bool amcanreturn; /* can AM return IndexTuples? */ |