[PostGIS] #5873: Postgres Topology and logical partitioning

[PostGIS]

#5873: Postgres Topology and logical partitioning
--------------------------------+------------------
  Reporter:  Lars Aksel Opsahl  |      Owner:  strk
      Type:  enhancement        |     Status:  new
  Priority:  medium             |  Milestone:
 Component:  topology           |    Version:
Resolution:                     |   Keywords:
--------------------------------+------------------
Comment (by robe):

 If I am understanding this need correctly, you would like for some
 situations the 20 topologies to be treated as one topology and then in
 other occassions be treated as separate topologies.

 All this would require them to have IDs that don't overlap with each
 other, correct?  Which would mean we would need  face ids to be bigints.

 They could use the same sequencer, or they could use separate sequencers
 that start at different numbering to ensure they don't overlap.  Probably
 better for separate sequencer.

 and there would be a new thing, called a "Spatial Grid" that denotes the
 boundaries of each topology and the sequence ranges of each.

 You would build on the existing  table partitioning in PostgreSQL, which I
 think would be not too hard since all topologies have the same structure
 anyway and use the ids as a partitioning key.


 If  you filter for a location in the grid, it would tell you you only need
 to touch topologies 1 and 2 so there would be a prefilter that filters
 only for say faces that are within the range of topologies 1 and 2.

 That would force the system to ignore the other 18 topologies you have.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5873#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.