[postgis-tickets] [PostGIS] #2724: PostGIS specific background workers

[PostGIS]

#2724: PostGIS specific background workers
-------------------------+--------------------------------------------------
 Reporter:  robe         |       Owner:  pramsey      
     Type:  enhancement  |      Status:  new          
 Priority:  medium       |   Milestone:  PostGIS 2.2.0
Component:  postgis      |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------
Description changed by robe:

Old description:

> Snooping on pgadvocacy http://www.postgresql.org/message-id/CAFj8pRA8
> +J17PxmmL1B8b-4bfbHvpQPcp7g7rG7Skune=BuY8Q at mail.gmail.com  got me
> thinking.
>
> I admit to not having looked at the background API coming in PostgreSQL
> 9.4.  So this is more of a placeholder to investigate, see how useful it
> is, and if useful add to PostGIS 2.2  additional extensions only
> installed for those folks running PostgreSQL 9.4+.
>
> Areas I see where background workers might be useful are in obviously
> long running processes where running in a single transaction is bloody
> slow and the work needs to be broken up into separate runs.
>
> 1) raster processing
> 2) topology processing
> 3) tiger geocoder processing
>
> I suspect we'd probably need separate background workers for each
> tailored to the unique needs of each, but perhaps not.
>
> Thoughts?

New description:

 Snooping on pgadvocacy http://www.postgresql.org/message-id/CAFj8pRA8
 +J17PxmmL1B8b-4bfbHvpQPcp7g7rG7Skune=BuY8Q at mail.gmail.com  got me
 thinking.

 I admit to not having looked at the background API in PostgreSQL 9.3+.  So
 this is more of a placeholder to investigate, see how useful it is, and if
 useful add to PostGIS 2.2  additional extensions only installed for those
 folks running PostgreSQL 9.3+.

 Areas I see where background workers might be useful are in obviously long
 running processes where running in a single transaction is bloody slow and
 the work needs to be broken up into separate runs.

 1) raster processing
 2) topology processing
 3) tiger geocoder processing

 I suspect we'd probably need separate background workers for each tailored
 to the unique needs of each, but perhaps not.

 Thoughts?

--

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