Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL windows native port available

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Robert Collins" <robert(dot)collins(at)itdomain(dot)com(dot)au>,<jm(dot)poure(at)freesurf(dot)fr>, <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL windows native port available
Date: 2002-05-10 11:02:31
Message-ID: 214E9C0A75426D47A876A2FD8A07426E9751@salem.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Robert Collins [mailto:robert(dot)collins(at)itdomain(dot)com(dot)au] 
> Sent: 10 May 2002 11:56
> To: Dave Page; jm(dot)poure(at)freesurf(dot)fr; pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] PostgreSQL windows native port 
> available
> 
> 
> > Installer technologies aside, one of the major reasons for
> > this (and the other discussions on pgsql-hackers) is the wish 
> > to 'hide' Cygwin from the PostgreSQL user. We need to make it 
> > live in C:\Program Files\PostgreSQL, not have a complete unix 
> > style file layout, and generally look like a real Windows 
> > application. Cygwin is a great environment for working in and 
> > porting software, but now that work is done, PostgreSQL (as 
> > an application) should use, and expose the absolute minimum 
> > of Cygwin to the user.
> 
> You should rebuild cygwin with a different shared memory area 
> then, to avoid the -inevitable- shared memory area versioning 
> conflicts that will arise. Cygwin1.dll needs to share data 
> across process's, and that is done via a named shared memory 
> area. If your copy of cygwin1.dll is different to a version 
> the user installs elsewhere, you will have trouble (unless 
> you've rebuilt cygwin with a different memory area).
> 
> I'd suggest that you simply install cygwin in it's usual 
> place, and forget about it... Anyway, that's a different 
> issue as it is orthogonal to the installer that is used.

To be honest, if I get involved at all it will only be from a packaging
pov - there are others far more qualified than me who are looking at how
exactly the port should be built, ie. Should we change at all, should we
use a cutdown version or the current package (my opinion obviously), or
should we write our own IPC, & fork() etc.

> BTW: Jason Tishler may be interested in what you are doing, 
> he maintains the current Cygwin postgreSQL port.

Yes, I exchanged email on the subject with Jason yesterday.

Regards, Dave.

pgadmin-hackers by date

Next:From: Buchanan, KimbaDate: 2002-05-17 15:03:33
Subject: pgmigrate from command line for visual basic
Previous:From: Robert CollinsDate: 2002-05-10 10:56:06
Subject: Re: PostgreSQL windows native port available

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group