I have a pretty similar question compared to this one: Publish multiple tables from different PostgreSQL's schemas on GeoServer

The main difference is the amount of databases. Question above has only 4. I do have a lot more which will pretty much invalidate all the answers to that question.

So I will just repeat the above question changed in a way it matches my situation:

I have about 30 tables times 50 databases in PostGIS. I know that every PostGIS store must be connected with just one schema/database.

The reason we have 50 databases is the multitenancy setup. I do not want to put two customers in 1 database. Therefore the GeoServer workspace for every database also needs to be different.

What now happens is that the amount of connections to PostgreSQL (with PostGIS) will all get allocated, so that extra connections get blocked.

I know I can increase PostgreSQL's connection limit, but I'm not sure that I want to do that.

What is the most efficient way to publish these tables from different databases (and thus schemas) on GeoServer?

  • How do you come to that conclusion "the GeoServer workspace for every database also needs to be different". That is not true. You need new datastores for each table, but these can be in the same workspace.
    – pLumo
    Feb 15, 2018 at 15:54
  • It's a requirement. RoVo Feb 15, 2018 at 17:36

1 Answer 1


If there are different databases, and they are a requirement, increasing the amount of allowed connections is pretty much the only way to go, as far as I know.

  • Same thought as I had, but I was hoping for a better way. I think using PgBouncer/PgPool or JDNI, all have no major benefit because they also need seperate connections for each database. Feb 17, 2018 at 13:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.