[postgis-tickets] [PostGIS] #2709: Crash (more often under high loads)

[PostGIS]

#2709: Crash (more often under high loads)
----------------------+-----------------------------------------------------
 Reporter:  bshankle  |       Owner:  pramsey      
     Type:  defect    |      Status:  new          
 Priority:  blocker   |   Milestone:  PostGIS 2.1.3
Component:  postgis   |     Version:  2.1.x        
 Keywords:            |  
----------------------+-----------------------------------------------------

Comment(by pramsey):

 In general, I think the only way to track this down will be to valgrind
 the backend while running this query. Because it's a concurrency problem,
 I tend to think it's a result of a function writing outside its allocated
 memory, over top of the working memory of another backend, then boom. So
 getting a stack trace from the dying back-end won't tell you where the
 problem happened (the writing outside memory). What's needed is to
 carefully watch what happens when a single backend runs the query: does it
 write outside memory it should? PostgreSQL 9.4 does include valgrind
 support (they say) so hopefully can be used to figure out if we have a
 memory fubar.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2709#comment:3>
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.