> > 1. Cygwin's setup.exe supports categories and dependencies.
> > Hence, there is no reason to install all Cygwin packages in
> > order to ensure properly PostgreSQL operation. Someone just
> > has to determine what is the minimal set of packages
> > necessary for PostgreSQL and I will update the setup.hint
> > accordingly. The current setup.hint is as follows:
> >
> > sdesc: "PostgreSQL Data Base Management System"
> > category: Database
> > requires: ash cygwin readline zlib libreadline5
> >
> > Sorry, but since I install all Cygwin packages plus about 30
> > additional ones I haven't desire to determine what are the
> > minimal requirements.
If no one else has done this, I'll be happy to dig in and answer this.
> > 2. Cygwin's setup.exe is customizable. There is a tool
> > called "upset" that generates the setup.ini file that drives
> > setup.exe. PostgreSQL could offer a customized setup. For
> > example, this is what the XEmacs folks are doing.
This is a great start to a more Win-feeling PG.
> > 3. Cygwin's setup.exe can run package specific postinstall
> > scripts during the installation. Hence, someone could
> > automate the steps enumerated (e.g., postmaster NT service
> > installation, initdb, etc.) in my README:
> >
>
> http://www.tishler.net/jason/software/postgresql/postgresql-7.2.1.README
This is a great document. I had missed this before.
>
> Specifically, he indicates the following:
>
> BTW, Up through 40 users, PostgreSQL under CYGWIN using the TPC-C
> benchmark performed very much the same as Linux PostgreSQL on the
> exact hardware.
Interesting. Does anyone that has mentioned poor performance on cygwin have
any numbers to dispute this?
> Jason
Thanks for the info, and thanks for your work on the PG + cygwin stuff!
- J.
Joel BURTON | joel@joelburton.com | joelburton.com | aim: wjoelburton
Knowledge Management & Technology Consultant
