artemp/mapnik — Issue #863: pool configuration could be an api call (rather than set in layer XML)
Author: artemp
Created: 2011-10-11 16:39:23+00:00
State: open
Labels: Core_Library

After the bugfix as part of #855, it is now possible for servers that use more than 10 rendering threads to max out the default max_size of 10 for the postgres pool, leading to undefined behavior.

So, even after this is fixed (#862), it would still be more ideal for the calling application to be able to set the pool max_size, because this is actually a global setting and only the calling application that knows the # of potential threads that may operate concurrently (not the stylesheet author).