Re: [GENERAL] PostgreSQL run as process in windows

2013-01-07 Thread Craig Ringer
On 01/03/2013 12:51 PM, tuanhoanganh wrote: > On Thu, Jan 3, 2013 at 11:04 AM, John R Pierce > wrote: > > of course, a pooler only works right if the client applications > are modified to open a connection, do a transaction, and close the > connection. if t

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-07 Thread Craig Ringer
On 01/03/2013 04:46 PM, Alban Hertroys wrote: > FYI: There's a kernel sockets leak in the 64-bit edition of that OS in > combination with multiple CPU cores (meaning on any slightly modern > CPU). You might be running into that now or later. > See: http://support.microsoft.com/?id=2577795 > > The i

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-04 Thread Jeff Janes
On Wednesday, January 2, 2013, John R Pierce wrote: > On 1/2/2013 7:45 PM, Craig Ringer wrote: > >> 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

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-03 Thread Alban Hertroys
FYI: There's a kernel sockets leak in the 64-bit edition of that OS in combination with multiple CPU cores (meaning on any slightly modern CPU). You might be running into that now or later. See: http://support.microsoft.com/?id=2577795 The issue is over a year old and there's still no Windows upda

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-02 Thread tuanhoanganh
On Thu, Jan 3, 2013 at 11:52 AM, Craig Ringer wrote: > What's your host Windows OS? Windows Server 2008 R2? Windows 7? > I am runing Windows Server 2008 R2

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-02 Thread Craig Ringer
On 01/03/2013 12:16 PM, tuanhoanganh wrote: > On Thu, Jan 3, 2013 at 10:45 AM, Craig Ringer > 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

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-02 Thread tuanhoanganh
On Thu, Jan 3, 2013 at 11:04 AM, John R Pierce wrote: > of course, a pooler only works right if the client applications are > modified to open a connection, do a transaction, and close the connection. > if the clients continue to hold idle connections, the pooler won't do > anything useful for y

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-02 Thread tuanhoanganh
On Thu, Jan 3, 2013 at 10:45 AM, Craig Ringer 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

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-02 Thread John R Pierce
On 1/2/2013 7:45 PM, Craig Ringer wrote: 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. 2nd and 3rd the emoti

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-02 Thread Craig Ringer
On 01/03/2013 10:40 AM, tuanhoanganh wrote: > Hello all. > I have more than 500 users connect to Postgres in windows 2008 R2. I > change registry make postgres service support 512 connect. But is > there any good way make postgres run as process not service. Is it > safe run postgres as process in

Re: [GENERAL] PostgreSQL run as process in windows

2013-01-02 Thread John R Pierce
On 1/2/2013 6:40 PM, tuanhoanganh wrote: I have more than 500 users connect to Postgres in windows 2008 R2. I change registry make postgres service support 512 connect. But is there any good way make postgres run as process not service. Is it safe run postgres as process in windows. a service