diff options
| author | Noah Misch <noah@leadboat.com> | 2023-10-14 16:33:51 -0700 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2023-10-14 16:33:54 -0700 |
| commit | 782be0f7124a7e45acf122c1f4988937b94ddb4e (patch) | |
| tree | ad84132daf3d77aa3429e40c594b9119a3013677 /src/backend/jit/llvm/llvmjit_expr.c | |
| parent | 1102f4ece30ed734ca2193fedac74395490aee99 (diff) | |
| download | postgresql-782be0f7124a7e45acf122c1f4988937b94ddb4e.tar.gz postgresql-782be0f7124a7e45acf122c1f4988937b94ddb4e.zip | |
Dissociate btequalimage() from interval_ops, ending its deduplication.
Under interval_ops, some equal values are distinguishable. One such
pair is '24:00:00' and '1 day'. With that being so, btequalimage()
breaches the documented contract for the "equalimage" btree support
function. This can cause incorrect results from index-only scans.
Users should REINDEX any btree indexes having interval-type columns.
After updating, pg_amcheck will report an error for almost all such
indexes. This fix makes interval_ops simply omit the support function,
like numeric_ops does. Back-pack to v13, where btequalimage() first
appeared. In back branches, for the benefit of old catalog content,
btequalimage() code will return false for type "interval". Going
forward, back-branch initdb will include the catalog change.
Reviewed by Peter Geoghegan.
Discussion: https://postgr.es/m/20231011013317.22.nmisch@google.com
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions