After about a week of installing PostgreSQL, migrating from the single-user edition to server edition (converting databases), researching and implementing a backup strategy and overall familiarization with my new server setup, I got back to the business of photo collection curation.
One task is geo-location details and as I went back to work on this, I got the following error(s):
Too many clients? Huh? I had one client open on the server machine (MacPro). I checked the licenses in use under User Management; it showed 2 Loaded, 1 Available, 1 In Use.
No other clients are connected to the database server.
The error immediately came up as soon as I hit the Apply button after changing some geo details on 130 images.
Any ideas about what may be happening???
Errors during Geo-Tagging
Errors during Geo-Tagging
Photo Supreme V6.x Server Edition
PostgreSQL 12
macOS 11.1 (Big Sur)
Mac Pro (Late 2013), 3.0 GHz 8-Core Xeon E5, 64 GB DDR3
MacBook Pro (Mid 2015), 2.5 GHz Quad-Core i7, 16 GB DDR3L
PostgreSQL 12
macOS 11.1 (Big Sur)
Mac Pro (Late 2013), 3.0 GHz 8-Core Xeon E5, 64 GB DDR3
MacBook Pro (Mid 2015), 2.5 GHz Quad-Core i7, 16 GB DDR3L
Re: Errors during Geo-Tagging
This is a message from the database.
Increase the max_connections Setting in your PostgreSQL config. Also see the installation instructions for the Server Edition with PostgreSQL
Increase the max_connections Setting in your PostgreSQL config. Also see the installation instructions for the Server Edition with PostgreSQL
Re: Errors during Geo-Tagging
Hert,
Yes, I followed the recommendation in the PostgreSQL Installation Manual, but apparently it wasn't enough for the max_connections (50 x # of concurrent users = 100). So I bumped it up to 250 and that seems to have taken care of the errors.
Thanks again for the support Hert! Again very impressed with your prompt responses for support.
Yes, I followed the recommendation in the PostgreSQL Installation Manual, but apparently it wasn't enough for the max_connections (50 x # of concurrent users = 100). So I bumped it up to 250 and that seems to have taken care of the errors.
Thanks again for the support Hert! Again very impressed with your prompt responses for support.
Photo Supreme V6.x Server Edition
PostgreSQL 12
macOS 11.1 (Big Sur)
Mac Pro (Late 2013), 3.0 GHz 8-Core Xeon E5, 64 GB DDR3
MacBook Pro (Mid 2015), 2.5 GHz Quad-Core i7, 16 GB DDR3L
PostgreSQL 12
macOS 11.1 (Big Sur)
Mac Pro (Late 2013), 3.0 GHz 8-Core Xeon E5, 64 GB DDR3
MacBook Pro (Mid 2015), 2.5 GHz Quad-Core i7, 16 GB DDR3L
Re: Errors during Geo-Tagging
Yeah, the current system seems to require roughly 250 - 300 connections to allow for larger workloads like copying large(r) batches of files to drives or updating large(r) batches of files with tags etc.
@Hert, perhaps the lower limit of 250 could be mentioned as a tip in the documentation.
@Hert, it would be awesome if we could get DB control parameters in the client application, so that the application manages some of these workloads within the scope of the actual DB setting, as to prevent out of memory and too many client exceptions. Is there already some Mantis ticket about this?
@Hert, perhaps the lower limit of 250 could be mentioned as a tip in the documentation.
@Hert, it would be awesome if we could get DB control parameters in the client application, so that the application manages some of these workloads within the scope of the actual DB setting, as to prevent out of memory and too many client exceptions. Is there already some Mantis ticket about this?