Thread: PostgreSQL and Cygwin stability as a production db

PostgreSQL and Cygwin stability as a production db

From
Alan Caudill
Date:

Does anyone have experience running PostgreSQL on Cygwin in a production environment they can share?

 

I have an existing application that uses an embedded PostgreSQL db and want to do a Windows (Win2k) version.  I'm less concerned with install issues, but would like to know about stability and performance.  I'm especially concerned with stability over the long term.

 

Thanks.

 

            -Alan

Re: PostgreSQL and Cygwin stability as a production db

From
"Henshall, Stuart - WCP"
Date:

Hello,
        I run a ~30 users db on PostgreSQL+Cygwin+NT4 on a proliant. The only real problem I have had is that the postmaster doesn't always seem to have enough time to terminate its children during reboot, so you can end up leaving the postmaster.pid file. The major limitations are a 63 Process fork limit and the fact cygwin's fork actually copies memory (plus fiddles some file descriptors) makes connections slower.

hth,
- Stuart

-----Original Message-----
From: Alan Caudill [mailto:acaudill@centerrun.com]

Does anyone have experience running PostgreSQL on Cygwin in a production environment they can share?
 
I have an existing application that uses an embedded PostgreSQL db and want to do a Windows (Win2k) version.  I'm less concerned with install issues, but would like to know about stability and performance.  I'm especially concerned with stability over the long term.

 
Thanks.
 
            -Alan

Re: PostgreSQL and Cygwin stability as a production db

From
"Henshall, Stuart - WCP"
Date:

Sorry to reply to myself, but I just thought to mention that I used rename rather than the link option in xlog.c.
- Stuart

-----Original Message-----
From: Henshall, Stuart - WCP [mailto:SHenshall@westcountrypublications.co.uk]
Sent: 06 June 2002 10:35
To: 'Alan Caudill'; 'pgsql-cygwin@postgresql.org'
Subject: Re: [CYGWIN] PostgreSQL and Cygwin stability as a production db

Hello,
        I run a ~30 users db on PostgreSQL+Cygwin+NT4 on a proliant. The only real problem I have had is that the postmaster doesn't always seem to have enough time to terminate its children during reboot, so you can end up leaving the postmaster.pid file. The major limitations are a 63 Process fork limit and the fact cygwin's fork actually copies memory (plus fiddles some file descriptors) makes connections slower.

hth,
- Stuart
-----Original Message-----
From: Alan Caudill [mailto:acaudill@centerrun.com]
Does anyone have experience running PostgreSQL on Cygwin in a production environment they can share?
 
I have an existing application that uses an embedded PostgreSQL db and want to do a Windows (Win2k) version.  I'm less concerned with install issues, but would like to know about stability and performance.  I'm especially concerned with stability over the long term.

 
Thanks.
 
            -Alan

Re: PostgreSQL and Cygwin stability as a production db

From
Jason Tishler
Date:
On Thu, Jun 06, 2002 at 03:33:47PM +0100, Henshall, Stuart - WCP wrote:
> Sorry to reply to myself, but I just thought to mention that I used rename
> rather than the link option in xlog.c.

As soon as Bruce (hopefully) accepts the patch for the above, I will
release a new 7.2.1 to finally put this one to bed.

Jason

Re: PostgreSQL and Cygwin stability as a production db

From
Alan Caudill
Date:

Do you have any specifics on the user behavior?

Are there a lot of connections from those users, or just a few long-lived connections?    

How much data is moved around (updates/inserts)?

And how often do you reboot (and is it related to the db)?

 

Thanks for the input.

 

            -Alan

 

 

-----Original Message-----
From: Henshall, Stuart - WCP [mailto:SHenshall@westcountrypublications.co.uk]
Sent:
Thursday, June 06, 2002 1:35 AM
To: 'Alan Caudill'; 'pgsql-cygwin@postgresql.org'
Subject: RE: [CYGWIN] PostgreSQL and Cygwin stability as a production db

 

Hello,
        I run a ~30 users db on PostgreSQL+Cygwin+NT4 on a proliant. The only real problem I have had is that the postmaster doesn't always seem to have enough time to terminate its children during reboot, so you can end up leaving the postmaster.pid file. The major limitations are a 63 Process fork limit and the fact cygwin's fork actually copies memory (plus fiddles some file descriptors) makes connections slower.

hth,
- Stuart

-----Original Message-----
From: Alan Caudill [mailto:acaudill@centerrun.com]

Does anyone have experience running PostgreSQL on Cygwin in a production environment they can share?
 
I have an existing application that uses an embedded PostgreSQL db and want to do a Windows (Win2k) version.  I'm less concerned with install issues, but would like to know about stability and performance.  I'm especially concerned with stability over the long term.

 
Thanks.
 
            -Alan