| From: | tuanhoanganh <hatuan05(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL run as process in windows |
| Date: | 2013-01-03 04:16:03 |
| Message-ID: | CAJg-yaNsFRkcJYZJDW+CYX+sU4PG_1=EN=4HxnZ5cf+YafLM3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 3, 2013 at 10:45 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> Running PostgreSQL directly via pg_ctl, not as a service, will not
> change how it performs under load at all. It will not help you service
> more than 500 concurrent connections.
>
> You really need to put a connection pool in place to limit the number of
> concurrent workers. Look at PgBouncer or PgPool-II. As far as I know
> neither of them runs on Windows; you might want to think about a Linux
> box as a front-end.
>
Thanks for your help. But when use PgBouncer, it run as service and may be
it only support 512 connect (Because windows service only support default
125 connect, change registry windows can support 512 connect).
Is there any other way?
Thanks you very much (Sorry for my English)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tuanhoanganh | 2013-01-03 04:51:56 | Re: PostgreSQL run as process in windows |
| Previous Message | John R Pierce | 2013-01-03 04:04:25 | Re: PostgreSQL run as process in windows |