From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Could pgsql jdbc support pool reauthentication? |
Date: | 2017-10-31 11:00:02 |
Message-ID: | b8b5ae5f-44a8-6d75-83e9-eb4e36a7f966@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 31/10/2017 12:56, Álvaro Hernández Tortosa wrote:
>
>
> On 31/10/17 10:08, Achilleas Mantzios wrote:
>> Hello Vladimir, thanx
>>
>> On 31/10/2017 10:30, Vladimir Sitnikov wrote:
>>> Achilleas>So if say we need 5 connections max for the most complex app to work, and we have 200 users, then at peak time, the total number of connections would have to be raised to 1000.
>>>
>>> Pools can shrink, so you do not have to raise total number of connections to 1000 unless you truly expect 1000 concurrent connections.
>> I know, but we still risk having our max_connections exceeded. And this is not scaleable.
>
> That's true, but if you have a pgbouncer in front of PostgreSQL (you should) and the connections are used wisely (i.e. they are returned as soon as they finish the job, they don't sit idle) this
> is no longer a problem.
That would be a blessing if pgbouncer supported LDAP .
>
>
> Álvaro
>
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2017-10-31 11:08:36 | Re: Could pgsql jdbc support pool reauthentication? |
Previous Message | Álvaro Hernández Tortosa | 2017-10-31 10:56:30 | Re: Could pgsql jdbc support pool reauthentication? |