head	1.21;
access;
symbols
	REL7_4_29:1.15.4.6
	REL7_4_28:1.15.4.6
	REL7_4_27:1.15.4.6
	REL7_4_26:1.15.4.6
	REL7_4_25:1.15.4.6
	REL7_4_24:1.15.4.6
	REL7_4_23:1.15.4.6
	REL7_4_22:1.15.4.6
	REL7_4_21:1.15.4.6
	REL7_4_20:1.15.4.6
	REL7_3_21:1.14.4.5
	REL7_4_19:1.15.4.6
	REL7_3_20:1.14.4.5
	REL7_4_18:1.15.4.6
	REL7_3_19:1.14.4.5
	REL7_4_17:1.15.4.6
	REL7_3_18:1.14.4.5
	REL7_4_16:1.15.4.6
	REL7_4_15:1.15.4.6
	REL7_3_17:1.14.4.5
	REL7_4_14:1.15.4.6
	REL7_3_16:1.14.4.5
	REL7_3_15:1.14.4.5
	REL7_4_13:1.15.4.6
	REL7_3_14:1.14.4.5
	REL7_4_12:1.15.4.6
	REL7_3_13:1.14.4.5
	REL7_4_11:1.15.4.6
	REL7_3_12:1.14.4.5
	REL7_4_10:1.15.4.6
	REL7_3_11:1.14.4.5
	REL7_4_9:1.15.4.6
	REL7_2_8:1.14
	REL7_3_10:1.14.4.5
	REL7_4_8:1.15.4.6
	REL7_2_7:1.14
	REL7_3_9:1.14.4.5
	REL7_4_7:1.15.4.6
	REL7_4_6:1.15.4.6
	REL7_3_8:1.14.4.5
	REL7_2_6:1.14
	REL8_0_0BETA3:1.20
	REL8_0_0BETA2:1.20
	REL7_2_5:1.14
	REL7_4_5:1.15.4.6
	REL7_3_7:1.14.4.5
	REL7_4_4:1.15.4.6
	REL8_0_0BETA1:1.20
	REL7_4_3:1.15.4.6
	REL7_4_2:1.15.4.6
	REL7_3_6:1.14.4.5
	REL7_4_1:1.15.4.5
	REL7_3_5:1.14.4.5
	REL7_4:1.15.4.4
	REL7_4_RC2:1.15.4.1
	REL7_4_STABLE:1.15.0.4
	REL7_4_RC1:1.15
	REL7_4_BETA5:1.15
	REL7_4_BETA4:1.15
	REL7_4_BETA3:1.15
	REL7_4_BETA2:1.15
	WIN32_DEV:1.15.0.2
	REL7_4_BETA1:1.15
	REL7_3_4:1.14.4.5
	REL7_3_2:1.14.4.3
	REL7_2_4:1.14
	REL7_3_STABLE:1.14.0.4
	REL7_2_3:1.14
	REL7_2_STABLE:1.14.0.2
	REL7_2:1.14
	REL7_2_RC2:1.13
	REL7_2_RC1:1.13
	REL7_2_BETA5:1.13
	REL7_2_BETA4:1.13
	REL7_2_BETA3:1.12
	REL7_2_BETA2:1.12
	REL7_2_BETA1:1.11
	REL7_1_2:1.9.2.1
	REL7_1_STABLE:1.9.0.2
	REL7_1_BETA:1.2
	REL7_1_BETA3:1.2
	REL7_1_BETA2:1.2
	REL7_1:1.8;
locks; strict;
comment	@# @;


1.21
date	2004.10.08.15.58.21;	author momjian;	state dead;
branches;
next	1.20;

1.20
date	2004.07.20.22.56.40;	author momjian;	state Exp;
branches;
next	1.19;

1.19
date	2003.11.28.20.22.18;	author momjian;	state Exp;
branches;
next	1.18;

1.18
date	2003.11.13.03.53.00;	author momjian;	state Exp;
branches;
next	1.17;

1.17
date	2003.11.12.04.14.30;	author momjian;	state Exp;
branches;
next	1.16;

1.16
date	2003.11.09.03.47.51;	author momjian;	state Exp;
branches;
next	1.15;

1.15
date	2002.11.11.20.04.05;	author petere;	state Exp;
branches
	1.15.4.1;
next	1.14;

1.14
date	2002.02.02.20.34.16;	author momjian;	state Exp;
branches
	1.14.4.1;
next	1.13;

1.13
date	2001.12.05.18.23.40;	author momjian;	state Exp;
branches;
next	1.12;

1.12
date	2001.10.25.16.20.51;	author momjian;	state Exp;
branches;
next	1.11;

1.11
date	2001.05.11.22.27.12;	author petere;	state Exp;
branches;
next	1.10;

1.10
date	2001.05.07.16.02.38;	author momjian;	state Exp;
branches;
next	1.9;

1.9
date	2001.04.24.20.05.02;	author petere;	state Exp;
branches
	1.9.2.1;
next	1.8;

1.8
date	2001.04.03.18.14.39;	author momjian;	state Exp;
branches;
next	1.7;

1.7
date	2001.03.16.22.12.13;	author petere;	state Exp;
branches;
next	1.6;

1.6
date	2001.01.22.22.54.07;	author momjian;	state Exp;
branches;
next	1.5;

1.5
date	2001.01.22.03.36.58;	author momjian;	state Exp;
branches;
next	1.4;

1.4
date	2001.01.22.03.33.55;	author momjian;	state Exp;
branches;
next	1.3;

1.3
date	2001.01.19.23.43.35;	author petere;	state Exp;
branches;
next	1.2;

1.2
date	2000.10.18.21.14.56;	author momjian;	state Exp;
branches;
next	1.1;

1.1
date	2000.10.17.03.29.30;	author momjian;	state Exp;
branches;
next	;

1.9.2.1
date	2001.05.11.22.26.30;	author petere;	state Exp;
branches;
next	;

1.14.4.1
date	2002.11.11.19.59.56;	author petere;	state Exp;
branches;
next	1.14.4.2;

1.14.4.2
date	2002.11.16.02.34.22;	author momjian;	state Exp;
branches;
next	1.14.4.3;

1.14.4.3
date	2002.12.18.20.39.31;	author momjian;	state Exp;
branches;
next	1.14.4.4;

1.14.4.4
date	2003.02.14.14.05.52;	author momjian;	state Exp;
branches;
next	1.14.4.5;

1.14.4.5
date	2003.07.23.04.13.11;	author momjian;	state Exp;
branches;
next	;

1.15.4.1
date	2003.11.09.03.47.59;	author momjian;	state Exp;
branches;
next	1.15.4.2;

1.15.4.2
date	2003.11.12.04.14.34;	author momjian;	state Exp;
branches;
next	1.15.4.3;

1.15.4.3
date	2003.11.13.05.06.56;	author momjian;	state Exp;
branches;
next	1.15.4.4;

1.15.4.4
date	2003.11.14.18.07.48;	author momjian;	state Exp;
branches;
next	1.15.4.5;

1.15.4.5
date	2003.12.13.16.57.36;	author momjian;	state Exp;
branches;
next	1.15.4.6;

1.15.4.6
date	2004.03.05.19.57.20;	author momjian;	state Exp;
branches;
next	;


desc
@@


1.21
log
@Rename FAQ_MSWIN to FAQ_CYGWIN.
@
text
@How to install PostgreSQL on Windows
====================================

$Date: 2004/07/20 22:56:40 $

PostgreSQL requires the appropriate subset of Cygwin DLLs to be
installed in order that it functions under Windows.

This document assumes that you do not have Cygwin already installed
on your system.  If that is not the case, then you will need to
adjust these instructions accordingly.

1.  Download and run the Cygwin installer.  Visit http://cygwin.com/ and
    click on the "Install Cygwin now' link.  This will prompt you
    to download a "setup.exe".  Save this file somewhere on your
    system and then execute it.

2.  Proceed through the Cygwin install wizard.  Choose 'Install from
    Internet', specify a Local Package Directory and choose a mirror
    site that's close to you.  Answer the other installer questions
    appropriately for your configuration.

    When you come to the point of choosing which packages to install,
    expand the 'Database' section and click 'Skip' next to PostgreSQL
    to change it to the latest version of PostgreSQL available for
    Cygwin.

3.  Once the download and install process is complete, open a Cygwin
    shell and do the following for a basic installation:

    3a.  Start cygserver for shared memory support.  To do this,
         enter the command "/usr/sbin/cygserver &".  This program
         needs to be running anytime you start the PostgreSQL server
         (postmaster) or initialize a database (initdb).

    3b.  Use the initdb command to create a new database cluster.  An
         example command would be:

            initdb -D /usr/local/pgsql/data -W -E LATIN1

         Which will create a cluster in the /usr/local/pgsql/data
         directory, will prompt for a superuser password and will
         set the default database encoding to LATIN1.

    3c.  Start up the postmaster.  Use a command similar to the
         following:

            postmaster -D /usr/local/pgsql/data

         This will start the postmaster, and if successful you will
         see some initial log entries, and an entry "LOG: database
         system is ready".

4.  You are now running a PostgreSQL server on your Windows machine.

5.  It is possible to install cygserver and the postmaster as
    Windows NT services.  For information on how to do this, please
    refer to the README document included with Cygwin PostgreSQL.  It
    is installed in the /usr/share/doc/Cygwin directory.

Building from source
--------------------

There are some points that are only relevant if you are building Cygwin
PostgreSQL from source:

1.  Set your path to use the Cygwin bin directory before the Windows
    utilities.  This will help prevent problems with compilation.

2.  Proceed according to the INSTALL file (i.e., ./configure; make; etc.)
    noting the following Cygwin specific differences:

        o The GNU make command is called "make" not "gmake".
        o The adduser command is not supported -- use the appropriate
          user management application on Windows NT, 2000, or XP.
          Otherwise, skip this step.
        o The su command is not supported -- use ssh to simulate su
          on Windows NT, 2000, or XP. Otherwise, skip this step.

    Alternatively, proceed according to the README file supplied with
    the Cygwin PostgreSQL package.

Known issues
------------

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 or hangs. You can limit the number of connections
    using the MAX_CONNECTIONS option thus:

       make MAX_CONNECTIONS=5 check

    (On some systems you can have up to about 10 simultaneous connections).

3.  The default cygserver configuration may need to be changed (e.g.,
    increase SEMMNS) to prevent PostgreSQL from failing due to a lack of
    system resources.

Problem reports can be sent to pgsql-cygwin@@postgresql.org.
@


1.20
log
@As per the following:

    http://archives.postgresql.org/pgsql-cygwin/2004-07/msg00090.php

Jason Tishler
@
text
@d4 1
a4 1
$Date: 2003/11/28 20:22:18 $
@


1.19
log
@Attached is a patch to correct white space issues in FAQ_MSWIN.

Daniel Convissor
@
text
@d4 1
a4 1
$Date: 2003/11/13 03:53:00 $
d31 2
a32 2
    3a.  Start ipc-daemon2 for shared memory support.  To do this,
         enter the command "ipc-daemon2 &".  This program
d56 1
a56 1
5.  It is possible to install ipc-daemon2 and the postmaster as
d98 4
@


1.18
log
@Update MSWIN FAQ

Christopher Kings-Lynne
@
text
@d4 1
a4 1
$Date: 2003/11/12 04:14:30 $
d6 1
a6 1
PostgreSQL requires the appropriate subset of Cygwin DLLs to be 
d21 1
a21 1
    appropriately for your configuration. 
d31 3
a33 3
    3a.  Start ipc-daemon2 for shared memory support.  To do this, 
         enter the command "ipc-daemon2 &".  This program 
         needs to be running anytime you start the PostgreSQL server 
d39 1
a39 1
            initdb -D /usr/local/pgsql/data -W -E LATIN1 
d48 1
a48 1
            postmaster -D /usr/local/pgsql/data 
d91 1
a91 1
    refused errors or hangs. You can limit the number of connections 
@


1.17
log
@Here's some improvements.  I just ended up referring people to Jason's
website for install as service, because it's a quite a long and complex
process.

Christopher Kings-Lynne
@
text
@d4 1
a4 1
$Date: 2003/11/09 03:47:51 $
d58 2
a59 3
    refer to one of the README documents here:

	http://www.tishler.net/jason/software/postgresql/
@


1.16
log
@I have attached a more comprehensive MSWIN FAQ patch.  Basically, the
instructions were way out of date and incorrect.  Installing Postgres
from Cygwin is easier these days than the FAQ would imply.

This patch already includes Andrew's previous patch.

Christopher Kings-Lynne
@
text
@a2 1
$Date: 2002/11/11 20:04:05 $
d4 4
a7 2
PostgreSQL requires the Cygwin set of libraries to be installed in
order that it functions under Windows.
d20 2
a21 1
    site that's close to you.  Leave everything else as-is.
d29 1
a29 1
    shell and do the following:
d31 2
a32 3
    3a.  Start ipc-daemon2 for shared memory support. Use 
         "net start ipc-daemon2", if you want ipc-daemon2 installed 
         as a service; otherwise, use "ipc-daemon2 &".  This program 
d56 6
d69 1
a69 1
    utilities.  Cygwin sort must be used in preference to Windows sort.exe. 
@


1.15
log
@Revise platform FAQs.
@
text
@d3 1
a3 1
$Date: 2002/02/02 20:34:16 $
d5 2
a6 3
1.  Install the latest Cygwin package, available at http://cygwin.com/.
    The Cygwin package provides a UNIX-like API on top of the Win32
    API.
d8 3
a10 5
    A pre-built PostgreSQL is part of the standard Cygwin distribution
    and is installed by Cygwin's setup.exe.  You are encouraged to use
    this version unless it does not meet your needs.  Please read the
    README file, /usr/doc/Cygwin/postgresql-${version}.README, where
    "${version}" is the version (e.g., 7.2).
d12 4
a15 3
2.  Install the latest cygipc package, available at
    http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/cygipc/.
    Do not use versions prior to 1.04, they will not work.
d17 3
a19 1
    Use the following command to install the cygipc package:
d21 4
a24 1
        $ tar -C / -xjf cygipc-${version}.tar.bz2
d26 2
a27 1
    where "${version}" is the version (e.g., 1.11-1).
d29 5
a33 3
3.  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.
d35 2
a36 4
4.  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) or initialize a database (initdb).
d38 27
a64 1
5.  Proceed according to the INSTALL file (i.e., ./configure; make; etc.)
d77 2
a78 1
NOTE:  The following are known issues with PostgreSQL on Windows:
d83 1
a83 1
2.  make check can generate spurious regression test failures due to
d85 6
a90 1
    refused errors.
@


1.15.4.1
log
@I have attached a more comprehensive MSWIN FAQ patch.  Basically, the
instructions were way out of date and incorrect.  Installing Postgres
from Cygwin is easier these days than the FAQ would imply.

This patch already includes Andrew's previous patch.

Christopher Kings-Lynne
@
text
@d3 1
a3 1
$Date: 2002/11/11 20:04:05 $
d5 3
a7 2
PostgreSQL requires the Cygwin set of libraries to be installed in
order that it functions under Windows.
d9 5
a13 3
This document assumes that you do not have Cygwin already installed
on your system.  If that is not the case, then you will need to
adjust these instructions accordingly.
d15 3
a17 4
1.  Download and run the Cygwin installer.  Visit http://cygwin.com/ and
    click on the "Install Cygwin now' link.  This will prompt you
    to download a "setup.exe".  Save this file somewhere on your
    system and then execute it.
d19 1
a19 3
2.  Proceed through the Cygwin install wizard.  Choose 'Install from
    Internet', specify a Local Package Directory and choose a mirror
    site that's close to you.  Leave everything else as-is.
d21 1
a21 4
    When you come to the point of choosing which packages to install,
    expand the 'Database' section and click 'Skip' next to PostgreSQL
    to change it to the latest version of PostgreSQL available for
    Cygwin.
d23 1
a23 2
3.  Once the download and install process is complete, open a Cygwin
    shell and do the following:
d25 3
a27 5
    3a.  Start ipc-daemon2 for shared memory support. Use 
         "net start ipc-daemon2", if you want ipc-daemon2 installed 
         as a service; otherwise, use "ipc-daemon2 &".  This program 
         needs to be running anytime you start the PostgreSQL server 
         (postmaster) or initialize a database (initdb).
d29 4
a32 2
    3b.  Use the initdb command to create a new database cluster.  An
         example command would be:
d34 1
a34 27
            initdb -D /usr/local/pgsql/data -W -E LATIN1 

         Which will create a cluster in the /usr/local/pgsql/data
         directory, will prompt for a superuser password and will
         set the default database encoding to LATIN1.

    3c.  Start up the postmaster.  Use a command similar to the
         following:

            postmaster -D /usr/local/pgsql/data 

         This will start the postmaster, and if successful you will
         see some initial log entries, and an entry "LOG: database
         system is ready".

4.  You are now running a PostgreSQL server on your Windows machine.

Building from source
--------------------

There are some points that are only relevant if you are building Cygwin
PostgreSQL from source:

1.  Set your path to use the Cygwin bin directory before the Windows
    utilities.  Cygwin sort must be used in preference to Windows sort.exe. 

2.  Proceed according to the INSTALL file (i.e., ./configure; make; etc.)
d47 1
a47 2
Known issues
------------
d52 1
a52 1
2.  "make check" can generate spurious regression test failures due to
d54 1
a54 6
    refused errors or hangs. You can limit the number of connections 
    using the MAX_CONNECTIONS option thus:

       make MAX_CONNECTIONS=5 check

    (On some systems you can have up to about 10 simultaneous connections).
@


1.15.4.2
log
@Here's some improvements.  I just ended up referring people to Jason's
website for install as service, because it's a quite a long and complex
process.

Christopher Kings-Lynne
@
text
@d3 1
a3 1
$Date: 2003/11/09 03:47:59 $
d5 2
a6 2
PostgreSQL requires the appropriate subset of Cygwin DLLs to be 
installed in order that it functions under Windows.
d19 1
a19 2
    site that's close to you.  Answer the other installer questions
    appropriately for your configuration. 
d27 1
a27 1
    shell and do the following for a basic installation:
d29 3
a31 2
    3a.  Start ipc-daemon2 for shared memory support.  To do this, 
         enter the command "ipc-daemon2 &".  This program 
a54 6
5.  It is possible to install ipc-daemon2 and the postmaster as
    Windows NT services.  For information on how to do this, please
    refer to one of the README documents here:

	http://www.tishler.net/jason/software/postgresql/

d62 1
a62 1
    utilities.  This will help prevent problems with compilation.
@


1.15.4.3
log
@Update win32 include file on 7.4 branch.
@
text
@d3 1
a3 1
$Date: 2003/11/12 04:14:34 $
d57 3
a59 2
    refer to the README document included with Cygwin PostgreSQL.  It
    is installed in the /usr/share/doc/Cygwin directory.
@


1.15.4.4
log
@Update FAQ_MSWIN for 7.4 branch.
@
text
@d3 1
a3 2

$Date: 2003/11/13 03:53:00 $
@


1.15.4.5
log
@Stamp 7.4.1.

Update 7.4.1 FAQ's to current.
@
text
@d4 1
a4 1
$Date: 2003/11/28 20:22:18 $
d6 1
a6 1
PostgreSQL requires the appropriate subset of Cygwin DLLs to be
d21 1
a21 1
    appropriately for your configuration.
d31 3
a33 3
    3a.  Start ipc-daemon2 for shared memory support.  To do this,
         enter the command "ipc-daemon2 &".  This program
         needs to be running anytime you start the PostgreSQL server
d39 1
a39 1
            initdb -D /usr/local/pgsql/data -W -E LATIN1
d48 1
a48 1
            postmaster -D /usr/local/pgsql/data
d91 1
a91 1
    refused errors or hangs. You can limit the number of connections
@


1.15.4.6
log
@Brand 7.4.2.  Release notes still need work.
@
text
@@


1.14
log
@Update for 7.2:

This fixes references to 7.1.3 (I think).  It also
modifies the japanese
FAQ, so I'm not sure if that's done correctly.

Chris
@
text
@d3 1
a3 1
$Date: 2001/12/05 18:23:40 $
d7 1
a7 2
    API.  Using older versions such as 1.0 or B20 might require extra
    efforts.
@


1.14.4.1
log
@Revise platform FAQs.
@
text
@d3 1
a3 1
$Date: 2002/02/02 20:34:16 $
d7 2
a8 1
    API.
@


1.14.4.2
log
@Update TODO/FAQ for 7.3 release.
@
text
@d3 1
a3 1
$Date: 2002/11/11 20:04:05 $
@


1.14.4.3
log
@Update Russian FAQ.  Update all FAQ's for 7.3.X branch.
@
text
@@


1.14.4.4
log
@Update FAQ's in head and 7.3.X.
@
text
@@


1.14.4.5
log
@Update all FAQ's for 7.3.4.
@
text
@@


1.13
log
@Attached is the FAQ_MSWIN patch as promised.  Hopefully, it is not too
little, too late...

Jason Tishler
@
text
@d3 1
a3 1
$Date: 2001/10/25 16:20:51 $
d14 1
a14 1
    "${version}" is the version (e.g., 7.1.3).
@


1.12
log
@Remove <> from FAQ_MSWIN, for Vince.
@
text
@d1 3
a3 3
How to install PostgreSQL on Windows NT or Windows 2000
=======================================================
$Date: 2001/05/11 22:27:12 $
d5 4
a8 1
1.  Install the Cygwin package.
d10 5
a14 7
    The Cygwin package provides a UNIX-like API on top of the Win32
    API.  It is available at http://sources.redhat.com/cygwin/.  At
    the time of this writing, it is recommended to use either version
    1.1.7, a snapshot built after 2001/02/05 12:36:41, or the 1.3.x series
    (when available).  Version 1.1.8 contains a bug that will prevent the
    server to work.  Using older versions such as 1.0 or B20 might require
    extra efforts.
d16 1
a16 1
2.  Install the cygipc package, available at
d20 6
d33 11
a43 1
    server (postmaster).
d45 2
a46 1
5.  Proceed according to the INSTALL file.  (./configure; make; etc.)
@


1.11
log
@no more Andy Piper tools
@
text
@d3 1
a3 1
$Date: 2001/05/07 16:02:38 $
d8 1
a8 1
    API.  It is available at <http://sources.redhat.com/cygwin/>.  At
d16 1
a16 1
    <http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/cygipc/>.
d39 1
a39 1
Problem reports can be sent to <pgsql-cygwin@@postgresql.org>.
@


1.10
log
@Update FAQ to use new pgsql-cygwin@@postgresql.org list.
@
text
@d3 1
a3 1
$Date: 2001/04/24 20:05:02 $
d19 1
a19 5
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.

4.  The Cygwin bin directory has to be placed in the path before the
d23 1
a23 1
5.  Start ipc-daemon from the cygipc package.  Use "net start ipc-daemon",
d28 1
a28 1
6.  Proceed according to the INSTALL file.  (./configure; make; etc.)
@


1.9
log
@typological errors
@
text
@d3 1
a3 1
$Date: 2001/04/03 18:14:39 $
d43 1
a43 1
Problem reports can be sent to <pgsql-ports@@postgresql.org>.
@


1.9.2.1
log
@no more Andy Piper tools
@
text
@d3 1
a3 1
$Date: 2001/04/24 20:05:02 $
d19 5
a23 1
3.  The Cygwin bin directory has to be placed in the path before the
d27 1
a27 1
4.  Start ipc-daemon from the cygipc package.  Use "net start ipc-daemon",
d32 1
a32 1
5.  Proceed according to the INSTALL file.  (./configure; make; etc.)
d43 1
a43 1
Problem reports can be sent to <pgsql-cygwin@@postgresql.org>.
@


1.8
log
@See attached for a minor documentation patch that more accurately reflects
the current state of and the issues with PostgreSQL on Windows.

Thanks,
Jason

--
Jason Tishler
@
text
@d1 3
a3 3
How do I installing PostgreSQL on Windows NT or Windows 2000?
=============================================================
$Date: 2001/03/16 22:12:13 $
d40 1
a40 1
    overflowing the the listen() backlog queue which causes connection
@


1.7
log
@Make note that version 1.1.8 doesn't work.
@
text
@d3 1
a3 1
$Date: 2001/01/22 22:54:07 $
d10 4
a13 3
    1.1.7 or the 1.3.x series.  Version 1.1.8 contains a bug that will
    prevent the server to work.  Using older versions such as 1.0 or
    B20 might require extra efforts.
d27 2
a28 1
5.  Start `ipc-daemon &' (background process) from the cygipc package.
d34 1
a34 2
NOTE:  There are two issues with Cygwin's current UNIX domain socket
support:
d36 2
a37 2
1.  psql (and other clients) will hang if postmaster is not running and
    the socket file (e.g., /tmp/.s.PGSQL.5432) exists.
d39 3
a41 2
2.  Cygwin's AF_UNIX sockets are really implemented as AF_INET sockets
    so they are inherently insecure.
@


1.6
log
@Put back old MS FAQ>
@
text
@d3 1
a3 1
$Date: 2001/01/19 23:43:35 $
d8 5
a12 5
    API.  It is available at <http://sources.redhat.com/cygwin/>.
    The 1.1.x series is recommended (1.1.7 was the latest at the time
    of this writing); using 1.0 or B20 might require extra efforts.
    For B20 you also need to download the separate crypt library at the
    same location.
@


1.5
log
@Update.
@
text
@d1 3
a3 2
*  You can get the most recent version of this from
*  http://people.freebsd.org/~kevlo/postgres/portNT.html.
d5 1
a5 1
*  Problem reports can be sent to pgsql-ports@@postgresql.org.
d7 6
a12 2
How do I install the PostgreSQL server on Windows NT or Windows 2000?
=====================================================================
d14 28
a41 59
         Porting PostgreSQL to Windows 2000 installation procedures
                                      
   Thanks to Daniel Horak, JasonTishler ,Joost Kraaijeveld and Pete
   Formanfor their helps.
   Without them, I cannot port Postgres to Windows 2000 successfully.
   ______________________________________________________________________
   
     * Install the lastest verion(1.1.5) of Cygwin
       
               1. Click on the "Install Cygwin now" link on the
   http://sources.redhat.com/cygwinwebpage.
                    This downloads setup.exe to your system.
               2. Run setup and answer all of the questions. Please
   choose a mirror sitefor your download.
     * Install Charles Wilson's Cygwin32 IPC package
       
               1. Download the precompiled binary
   http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/cygipc/cygipc-
   1.07-1.tar.gzin"/" directory.
               2. tar zxvf cygipc-1.07-1.tar.gz
     * Install PostgreSQL 7.0.3
       
               1. Download PostgreSQL 7.0.3 sourcecode in /usr/src.
               2. tar zxvf postgresql-7.0.3.tar.gz
               3. mkdir -p /usr/local/pgsql/{bin,include,lib,data}
               4. cd /usr/src/postgresql-7.0.3/src/win32
               5. cp endian.h /usr/include
                    cp tcp.h /usr/include/netinet
                6. Apply Jason Tishler's patches  in
   /usr/src/postgresql-7.0.3, then run 'patch -p1 <patch.diff'.
                    Note that some browsers convert the patch to a text
   mode file (i.e., CRNL line endings)
                during the save operation which causes patch    to reject
   all hunks.
                7. cd /usr/src/postgresql-7.0.3/src, then run
   './configure'
               8. make; make install
               9. cp/usr/local/pgsql/lib/pq.dll /usr/local/pgsql/bin
             10. Usingany editor to create .bashrc in / directory as
   belows:
                     PATH=$PATH:/usr/local/pgsql/bin:/usr/local/bin
                     PGDATA=/usr/local/pgsql/data
                     PGLIB=/usr/local/pgsql/lib
                     LD_LIBRARY_PATH=/usr/local/pgsql/lib:/usr/local/lib
                     export LD_LIBRARY_PATH PATH PGDATA PGLIB
             11. source/.bashrc, then run 'initdb'
                    Note that the owner of the DB system have to be
   different from root/administrator
             12. Editthe file /usr/local/pgsql/data/pg_hba.conf, such as:
   
                    host        all     163.17.11.109   255.255.255.0
   trust
   
             13. ipc-daemon&
             14. postmaster-i&
             15. Run' psql -h host_name template1'. It's easy, huh :-)
   
   
                Last updated: 01/05/2001    Author: KevinLo
@


1.4
log
@Make Kevin Lo's MS FAQ the default.
@
text
@d4 1
a4 1
*  Problem reports can be sent to <pgsql-ports@@postgresql.org>.
@


1.3
log
@From Jason Tishler <jt@@dothill.com>

* doc/FAQ_MSWIN: Update to be consistent with software -- mainly change
comment from lack of Cygwin UNIX domain socket support and to list of
current Cygwin UNIX domain socket issues.
* src/include/config.h.in: Enable UNIX domain sockets for Cygwin.
* src/include/port/win.h: Disable UNIX domain sockets for Cygwin b20.1.
* src/test/regress/pg_regress.sh: Use UNIX domain sockets for Cygwin
instead of TCP/IP.
@
text
@d1 2
a2 3
How do I installing PostgreSQL on Windows NT or Windows 2000?
=============================================================
$Date: 2000/10/18 21:14:56 $
d4 1
a4 1
1.  Install the Cygwin package.
d6 2
a7 6
    The Cygwin package provides a UNIX-like API on top of the Win32
    API.  It is available at <http://sources.redhat.com/cygwin/>.
    The 1.1.x series is recommended (1.1.7 was the latest at the time
    of this writing); using 1.0 or B20 might require extra efforts.
    For B20 you also need to download the separate crypt library at the
    same location.
d9 59
a67 28
2.  Install the cygipc package, available at
    <http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/cygipc/>.
    Do not use versions prior to 1.04, they will not work.

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.

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.

5.  Start `ipc-daemon &' (background process) from the cygipc package.
    This program needs to be running anytime you start the PostgreSQL
    server (postmaster).

6.  Proceed according to the INSTALL file.  (./configure; make; etc.)

NOTE:  There are two issues with Cygwin's current UNIX domain socket
support:

1.  psql (and other clients) will hang if postmaster is not running and
    the socket file (e.g., /tmp/.s.PGSQL.5432) exists.

2.  Cygwin's AF_UNIX sockets are really implemented as AF_INET sockets
    so they are inherently insecure.

Problem reports can be sent to <pgsql-ports@@postgresql.org>.
@


1.2
log
@Make it an FAQ.
@
text
@d3 1
a3 1
$Date: 2000/10/17 03:29:30 $
d9 1
a9 1
    The 1.1.x series is recommended (1.1.4 was the latest at the time
d15 2
a16 2
    <http://cygutils.netpedia.net/V1.1/cygipc/>.  Do not use versions
    prior to 1.04, they will not work.
d32 8
a39 5
NOTE:  By default, PostgreSQL clients like psql communicate using Unix
domain sockets, which do not work on Windows.  Start the postmaster
with -i, and when connecting to the database from a client, set the
PGHOST environment variable to `localhost' or supply the hostname on
the command line.
@


1.1
log
@FAQ_MSWIN is better than INSTALL_MSWIN
@
text
@d1 3
a3 3
Installing PostgreSQL on Windows NT or Windows 2000
===================================================
$Date: 2000/10/17 03:26:36 $
@
