From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | Andy Colson <andy(at)squeakycode(dot)net> |
Cc: | sanjeetkamble <sanjeetkamble(at)rediffmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Setting up a database for 10000 concurrent users |
Date: | 2015-05-04 14:22:37 |
Message-ID: | CANu8FiwmP=dZzsVzUSouNt2JtSmnGRL_ubzGMZ4ZnGNi50Syrg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I suggest pg_bouncer as opposed to pg_pool. My testing showed it handled
connections better. Ultimately the choice is yours, but with 10000
connections, you absolutely need a connection manger.
On Mon, May 4, 2015 at 10:08 AM, Andy Colson <andy(at)squeakycode(dot)net> wrote:
> On 05/04/2015 02:02 AM, sanjeetkamble wrote:
>
>> Hello,
>>
>> Please let me know how The database server is started with
>> max_connections =
>> 10000 ???
>>
>> I have same issue, but i have a SAN storage where Postgresql is
>> installed.
>>
>>
>> Sanjeet
>>
>>
>>
> No doubt that would be a problem. Its bad idea. set max_connections to
> core count * 2, then put pg_pool in front, and set pg_pools max count to
> 10000.
>
> -Andy
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2015-05-04 14:33:06 | Re: Setting up a database for 10000 concurrent users |
Previous Message | Andy Colson | 2015-05-04 14:08:26 | Re: Setting up a database for 10000 concurrent users |