Opened 10 years ago
Closed 10 years ago
#3178 closed defect (fixed)
EWKB emitter should emit complex empty geometry
| Reported by: | pramsey | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.1.8 |
| Component: | postgis | Version: | master |
| Keywords: | Cc: |
Description
The EWKB emitter (which drives the backup/dump format) does not emit complex empty geometries (eg, MULTILINESTRING(EMPTY, EMPTY)) it simplifies them down to a single empty instance. As a result, it's not possible to dump/restore a database with complex empties without changing their form.
Change History (2)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I just had a severe debugging issue because of this. It looked very much like a local install or hardware issue, because it was impossible to replicate elsewhere. Turns out the replication issue was the inability to dump/restore the actual geometry. Since we can create these things, we need to allow them transit. Now, another approach might be to try to catch them at serialization and never allow them to be stored on disk at all. I've implemented the "simple" fix for now, which allows them out into WKB, when teh WKB variant is "EXTENDED" (the dump format).
Committed at r13701. Still leaves representing POINT EMPTY as NaN,NaN as a TBD task.
How common is this issue? Yah I know POINT EMPTY is common enough to be concerned but? I've never heard of this particular problem. Is this just a hypothetical issue or have you actually seen this in the wild?