
Yeah I know adding an extra piece of software to your stack is something
you'd like to avoid if not needed. However you indicate you're struggling
with limiting connections at the moment, so I'm sure it's worth it in this
case to add PgBouncer. In my experience, PgBouncer is easy to configure,
maintenance free and really stable. Apache::DBI exists but does not really
pool connections, it only makes them persistent per web server process.
--
Michiel
On Tue, Jun 7, 2016 at 10:36 AM, Lukasz Borek
Hi,
Thank You! We’re trying to avoid an extra software, but after digging all over internet I’m getting sure that we do not missed any otrs conf string that could manage it. Oh well, thanks for the reply! LG, Lucas
-------7 June 2016, . 10:08:
Hi Lukasz,
In my experience the nicest solution is to connect OTRS to PgBouncer and have PgBouncer do the connection pooling.
-- Michiel
On Mon, Jun 6, 2016 at 12:18 PM, Lukasz Borek
wrote: Hi there!
For some time we are struggling with limiting the amount of connections between our OTRS and Postgresql server. How can we limit/set up/manage pool size for connections to our db server? We’re unable to find any config for this. Any help would be very appreciated, LG, Lukasz Borek --------------------------------------------------------------------- OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm
--------------------------------------------------------------------- OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm
--------------------------------------------------------------------- OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm