Thanks to everyone who contributed to this thread, either on the PostGIS
[1] or the PostgreSQL [2] mailing lists. I will try to summarize everything
in this message, which I will actually post on both lists to give an update
to everyone. I hope it can be useful for other people interested.
Own setup : dell precision 2*6 cores, 20 go RAM, SSD for index, 7200 HDD
for big tables.
I do very different stuff with the server :
- base for visualisation of classical vector table (Usually few users
mostly reading.)
- base for automatic road generation (topology + very very complex query)
Hey,
nice project =)
If you use something like qgis, each user can easily have a dozen
connection open to server, so with 10 users, you may need to use something
like pgpool.
About hardware dimension, it is more a question for postgres list.
You may stress that your usage is probably mostly
Hey Rémi,
Thanks for the feedback! Exactly the type of information I'm looking for.
Before commenting further, if anyone has another experience about such a
multi-user PostGIS server in a small unit, please feel free to share! The
more I get from actual users, with different experience and
Others gave lots of good feedback, but let me chime in.
* I didn't know about pgpool. It looks like it may come in handy if there
connections become sluggish or simply impossible due to too many users. I
will definitely keep this under my hat, although I understand it is a
UNIX-only
You didn't talk about backup, it is essential (raid, replication, backup
script?).
I'm sorry to be that guy: RAID is NOT a backup. Unless you snapshot
your replication machine, replication isn't a backup either (though,
like RAID, it enables High Availability (HA)).
For lack of a precise
Dear PostGIS users,
I am currently planning to set up a PostGIS instance for my lab. Turns out
I believe this would be useful for the whole center, so that I'm now
considering setting up a PostGIS server for everyone—if interest is shared
of course. At the moment, I am however struggling with
