Re: [PORTS] Re: Quick question

I don't know anything about MS stuff, so whatever you guys decide is
fine by me. I will apply the patch.

> Bruce,
>
> On Tue, May 08, 2001 at 10:49:49PM -0400, Bruce Momjian wrote:
> >
> > Can someone evaluate this patch and generate a FAQ patch?
>
> See my comments below. If my suggestions are deemed acceptable, then I
> will generate a FAQ_MSWIN patch.
>
> > > How to install PostgreSQL on Windows NT >>>>>> 4.0 SP6a <<<<<<<
>
> Actually, I would recommend dropping the NT, 2000, etc. because AFAICT
> Cygwin PostgreSQL should run whenever Cygwin runs which is all Win32
> Intel versions.
>
> > > =======================================================
> > > $Date: >>>>>2001/05/07<<<<< $
>
> The above is just a RCS keyword and does not need to be changed.
>
> > >
> > > 1. Install the Cygwin package.
> > >
> > > The Cygwin package provides a UNIX-like API on top of the Win32
> > > API. It is available at <http://sources.redhat.com/cygwin/>.
> > > >>>>>>>>>> I used 1.3.1. <<<<<<<<
>
> I'm a little leery to recommend 1.3.1 at the moment (I still don't use
> it myself). But, soon the snapshots will all be newer than 1.3.1 anyway.
> Hence, I reluctantly recommend changing this to indicate using 1.3.1
> or later.
>
> > > >>>>>>>>>> I installed Cygwin using the administrator id,
> > > set the option to make Cygwin available to all users
> > > and installed all packages. <<<<<<<<<<
>
> The above seems superfluous so I don't recommend including this in
> FAQ_MSWIN.
>
> > > 2. Install the cygipc package, available at
> > > <http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/cygipc/>.
> > > >>>>>>> I used 1.09-2. When I first installed it,
>
> I recommend leaving this alone or adding "*latest* cygipc package."
> Otherwise, FAQ_MSWIN will have to be updated every time Chuck Wilson
> releases a new cygipc distribution.
>
> > > I used c:\usr and that created a problem
> > > so I changed to c:\cygwin\usr. I do not have a note of the exact problem. <<<<<<<<<
>
> I'm not sure what Peter means by the above, but as long a the user
> unpacks the cygipc tarball with a Cygwin tool (as opposed to a Win32 one
> such as WinZip) then he/she should not have any problems. I can add a
> suggested command line:
>
> $ tar -C / -xzf cygipc-1.09-2.tar.gz
>
> > > 3. Optional: The "Andy Piper Tools" at <http://www.xemacs.freeserve.co.uk/>
> > > are a collection of pre-compiled libraries and utilities that you
> > > might find useful -- especially on Cygwin B20.
> > > >>>>>>>>> Andy no longer has downloadable stuff at his site <<<<<<<<<<<<<<<<<
>
> I agree with Peter that the above should be removed.
>
> > > 4. The Cygwin bin directory has to be placed in the path before the
> > > Windows program directories, because the sort.exe has to be taken
> > > from Cygwin, not Windows.
> > > >>>>>> A PostgreSQL library has to go in the same path so make one change to:
> > > c:\cygwin\usr\local\pgsql\lib;c:\cygwin\bin;c:\winnt......
> > > <<<<<<<
>
> The above is *not* necessary if the user is using the PostgreSQL supplied
> with Cygwin. I post process make install to copy the appropriate DLLs
> (i.e., pq.dll) into usr/bin.
>
> > > 5. Start ipc-daemon from the cygipc package. Use "net start ipc-daemon",
> > > if ipc-daemon is installed as a service; otherwise, use "ipc-daemon &".
> > > This program needs to be running anytime you start the PostgreSQL
> > > server (postmaster).
> > > >>>> I logged in as administrator and ran "ipc-daemon --install-as-service" and it worked perfectly.
>
> The above comment is superfluous and should not be added to FAQ_MSWIN.
>
> > > 6. Proceed according to the INSTALL file. (./configure; make; etc.)
> > > >>> Note that all the commands in the INSTALL file have to be run
> > > in the Cygwin window, not the NT command line window.
>
> Not true -- only the shell scripts need special treatment such as
>
> C:\> bash configure
>
> Executables, such as make, run just fine from cmd.exe/command.com.
> Actually, there are tricks to make shell script run from a Windows
> shell...
>
> Nevertheless, I can add that it is recommended to proceed according to
> the INSTALL file in a bash shell. I can also add a blurb regarding the
> following steps:
>
> adduser postgres
> su - postgres
>
> and how they map onto NT.
>
> > > I ran the first part of the PostgreSQL install as administrator
> > > then created the database as administrator then could not access the database form my normal user id
> > > so I deleted the database and recreated the database from my normal logon and everything worked fine.
> > > <<<<<
>
> I believe that the above is just the normal requirement that postmaster
> and the database files must be owned by the same user. Hence, I don't
> recommend adding the above to FAQ_MSWIN.
>
> > > NOTE: The following are known issues with PostgreSQL on Windows:
> > >
> > > 1. Cygwin's AF_UNIX sockets are really implemented as AF_INET sockets
> > > so they are inherently insecure.
> > >
> > > 2. make check can generate spurious regression test failures due to
> > > overflowing the listen() backlog queue which causes connection
> > > refused errors.
> > >
> > > Problem reports can be sent to <pgsql-ports(at)postgresql(dot)org>.
> > > >>>> Email sent to this address bounced with some message about not being registered.<<<<<
>
> You have already corrected the email address. I don't know why
> Peter's email bounced unless the list is setup to only accept email
> from subscribers.
>
> Jason
>
> --
> Jason Tishler
> Director, Software Engineering Phone: +1 (732) 264-8770 x235
> Dot Hill Systems Corp. Fax: +1 (732) 264-8798
> 82 Bethany Road, Suite 7 Email: Jason(dot)Tishler(at)dothill(dot)com
> Hazlet, NJ 07730 USA WWW: http://www.dothill.com
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026