[postgis-users] QGIS + PostGIS in production environment

George Silva georger.silva at gmail.com
Fri Jun 16 05:39:17 PDT 2017

I would not split each toposheet in a single database.

You could divide them using schemas or partitioned tables. With partitioned
tables PostgreSQL is smart enough to query a single toposheet at the time,
perhaps giving you a boost on the server.

The slow saving times might be mitigated by using the pooler and tuning.

First of all, you should plan an update on your versions.

The second step I would do is to tune the db.

We have a simple open source project called cartohelper (
gitlab.sigmageosistemas.com.br) that automates a lot of things for large
scale cartography. Validations, issues, etc, but its for an outdated qgis.

That might give you some ideas on how to organize your database.

Em 15 de jun de 2017 11:32 PM, "Richard Greenwood" <
richard.greenwood at gmail.com> escreveu:

> On Thu, Jun 15, 2017 at 1:58 PM, Cap Diniz <diniz.felipe at eb.mil.br> wrote:
>> We are using Dell PowerEdge-R430 [1] for the PostGIS server with OS
>> Debian 8.7 on a 1gigabit network. For each topographic sheet we use one
>> database, this means that we have hundreds of databases in production.
> Why do you have some many different databases? I don't know what impact it
> would have on performance, but it seems like it would me challenging to
> manage.
> Rich
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20170616/44c58b8f/attachment.html>

More information about the postgis-users mailing list