[postgis-tickets] [PostGIS] #3650: Aggregate functions aren't marked as parallel safe

[PostGIS]

#3650: Aggregate functions aren't marked as parallel safe
----------------------+---------------------------
  Reporter:  komzpa   |      Owner:  robe
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.3.1
 Component:  postgis  |    Version:  2.3.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 I can do some quick queries with large datasets just to confirm no
 consequences and then I'll commit if it looks okay.

 I think there is some funky stuff with the PostgreSQL handling of parallel
 aggregates (it's PostgreSQL specific though).  For example when I was
 updating data (geocioding) , the counts of what geocoded was going up and
 down (when it should have been only increasing).  It was using a parallel
 strategy.  I was ignoring it for the most part, but have to revisit.

 I want to double check that to see if it only happens during updates. If
 it is a bug, I'd rather wait and implement this when 9.6.1 comes out.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3650#comment:2>
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.