Changes between Initial Version and Version 1 of Ticket #2269
- Timestamp:
- 04/09/13 11:33:52 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2269
- Property Milestone → PostGIS 2.0.4
- Property Owner changed from to
- Property Status new → assigned
-
Ticket #2269 – Description
initial v1 5 5 The call stack during the ANALYZE usually looks like this: 6 6 7 {{{ 7 8 (gdb) bt 8 9 #0 pglz_decompress (source=0x43f6bd98, dest=0x43fb5b2c "") at … … 64 65 postmaster.c:1127 65 66 #21 0x0000000000667225 in main (argc=2, argv=0x1227230) at main.c:199 67 }}} 66 68 67 69 PostGIS appears to leak memory for each tuple ANALYZED (or the memory context that allocation occurs within is not destroyed until the end of ANALYZE, which results in ballooning of memory consumption in practice).