I guess the main issue is if you're going to be having 20,000
simultaneous connections (unlikely).
If you're using Java then you can setup a connection pool for orders of
magnitude persistent connections less that that.
If using persistent connections in PHP or mod_perl, etc, you should
adjust apache's child lifetime so the processes will die after a few
thousand requests, thus keeping the number of connections to Postgresql
low.
The same strategy would apply if you are using any database. Even with
MySql you dont want 16,000 connections open :-)
- Ericson Smith
eric@did-it.com
On Thu, 2002-10-31 at 09:39, Reynard Hilman wrote:
>
> Hi,
>
> I need to set up a system that will be used by some 20,000 users. Most
> of the applications will be web based.
> I'm wondering if postgress will be able to handle 20,000 connection.
> MySQL has a max connection of about 16,000. Does postgres have a max
> connection limit? or does the limit depend on the hardware resources only?
> I wonder if using a cluster will help (something like oracle database
> cluster). I have search the mailing list for clustering, and found some
> articles
>
> http://archives.postgresql.org/pgsql-general/2000-12/msg00024.php
>
> but this was quite long time ago, and it seems like they are still in
> research.
> Has anyone done postgres clustering for a production use?
> It would be helpful to have a section explaining how to do this (if it's
> possible).
>
> thanks,
> - reynard
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
