Opened 10 years ago
Last modified 5 weeks ago
#3110 new enhancement
Use 64bit integers for identifiers
Reported by: | strk | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS Fund Me |
Component: | topology | Version: | master |
Keywords: | Cc: | aperi |
Description ¶
Topology primitive tables are created with 32bit integer identifiers. This ticket is to use 64bit integers instead.
Note that such change would also affect the relation table and the TopoElement and TopoElementArray domains.
An upgrade path should also be provided to alter existing topologies.
Change History (7)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Milestone: | PostGIS 2.2.0 → PostGIS 2.3.0 |
---|
comment:3 by , 9 years ago
Milestone: | PostGIS 2.3.0 → PostGIS 2.4.0 |
---|
comment:4 by , 8 years ago
Milestone: | PostGIS 2.4.0 → PostGIS 2.5.0 |
---|
comment:5 by , 7 years ago
Milestone: | PostGIS 2.5.0 → PostGIS 3.0.0 |
---|
comment:6 by , 6 years ago
Milestone: | PostGIS 3.0.0 → PostGIS Fund Me |
---|
comment:7 by , 5 weeks ago
We are researching migrating TIGER to POSTGIS, and would need IDs larger than the current integer. We do not need this for primitive IDs, but for consistency we can decide to use BIGINT (INT8) for all IDs, related tables, functions and types.
I have made local changes to our instance, but we will need this in the base product so we can use cloud services like AWS Aurora for our proof of concept.
I will be contributing these changes to the extension.
NOTE: sequences already use 64bit integers (bigint) so it is only a matter of using ALTER TABLE for the tables (and something for the domains)