PostGIS specific dynamic background workers
|Reported by:||robe||Owned by:||pramsey|
Description (last modified by )
Snooping on pgadvocacy http://www.postgresql.org/message-id/CAFj8pRA8+J17PxmmL1B8b-4bfbHvpQPcp7g7rG7Skune=BuY8Q@mail.gmail.com got me thinking.
I admit to not having looked at the background API 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.
Change History (6)
comment:3 Changed 3 years ago by
|Summary:||PostGIS specific background workers → PostGIS specific dynamic background workers|