Skip to content

Recover the uint64 PG typedef to uint64_t in the catalog#33

Merged
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:fix/recover-uint64-type
Jul 8, 2026
Merged

Recover the uint64 PG typedef to uint64_t in the catalog#33
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:fix/recover-uint64-type

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

A regression test (test_uint64_recovered) asserts the bare-uint64 *_hash_extended surface recovers to uint64_t, so a future refactor that drops the entry fails CI. Full suite: 148 passed, 14 skipped.

The type-recovery pass rewrites PG-vendored types that libclang collapses to
int back to their real spelling from the header text. uint64 was absent from
the recovery map, so every uint64 parameter and return (the raquet quadbin
cell, all *_hash_extended seeds and results, and other uint64 surfaces)
appeared as int in the catalog, truncating 64-bit values to 32 bits in the
generated bindings.

Add uint64 -> uint64_t, mirroring the existing int64 entry and the H3Index and
Quadbin entries that already recover to uint64_t, and add a regression test
that asserts the bare-uint64 *_hash_extended surface recovers to uint64_t.
@estebanzimanyi estebanzimanyi merged commit 1b65610 into MobilityDB:master Jul 8, 2026
2 checks passed
@estebanzimanyi estebanzimanyi deleted the fix/recover-uint64-type branch July 8, 2026 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant