installation on Windows It is recommended that most users download the binary distribution for Windows, available as a Windows Installer package from the PostgreSQL website. Building from source is only intended for people developing PostgreSQL or extensions. There are several different ways of building PostgreSQL on Windows. The complete system can be built using MinGW or Visual C++ 2005. It can also be built for older versions of Windows using Cygwin. Finally, the client access library (libpq) can be built using Visual C++ 7.1 or Borland C++ for compatibility with statically linked applications built using these tools. Building using MinGW or Cygwin uses the normal build system, see and the FAQs in doc/FAQ_MINGW and do/FAQ_CYGWIN. Note that Cygwin is not recommended, and should only be used for older versions of Windows where the native build does not work, such as Windows 98. The tools for building using Visual C++ 2005, are in the src/tools/msvc directory. When building, make sure there are no tools from MinGW or Cygwin present in your system PATH. Also, make sure you have all the required Visual C++ tools available in the PATH, usually by starting a Visual Studio Command Prompt and running the commands from there. All commands should be run from the src\tools\msvc directory. Before you build, edit the file config.pl to reflect the configuration options you want set, including the paths to libraries used. If you need to set any other environment variables, create a file called buildenv.bat and put the required commands there. For example, to add the path for bison when it's not in the PATH, create a file containing: @ECHO OFF SET PATH=%PATH%;c:\some\where\bison\bin PostgreSQL will build using either the professional versions (any edition) or the free Express edition of Visual Studio 2005. The following additional products are required to build the complete package. Use the config.pl to specify which directories the libraries are available in. ActiveState Perl ActiveState Perl is required to run the build generation scripts. MinGW or Cygwin Perl will not work. It must also be present in the PATH. Binaries can be downloaded from . ActiveState TCL Required for building PL/TCL. Bison and Flex Bison and Flex are required to build from CVS, but not required when building from a release file. Note that only Bison 1.875 or versions 2.2 and later will work. Bison and Flex can be downloaded from . Diff Diff is required to run the regression tests, and can be downloaded from . Gettext Gettext is required to build with NLS support, and can be downloaded from . Note that binaries, dependencies and developer files are all needed. Microsoft Platform SDK It is recommended that you upgrade to the latest available version of the Microsoft Platform SDK, available for download from . MIT Kerberos Required for Kerberos authentication support. MIT Kerberos can be downloaded from . libxml2 and libxslt Required for XML support. Binaries can be downloaded from or source from . Note that libxml2 requires iconv, which is available from the same download location. openssl Required for SSL support. Binaries can be downloaded from or source from . Python Required for building PL/Python. Binaries can be downloaded from . zlib Required for compression support in pg_dump and pg_restore. Binaries can be downloaded from . To build all of PostgreSQL in release configuration (the default), run the command: build To build all of PostgreSQL in debug configuration, run the command: build DEBUG To build just a single project, for example psql, run the commands: build psql build DEBUG psql To change the default build configuration to debug, put the following in the buildenv.bat file: set CONFIG=Debug It is also possible to build from inside the Visual Studio GUI. In this case, you need to run: perl mkvcbuild.pl from the command prompt, and then open the generated pgsql.sln (in the root directory of the source tree) in Visual Studio. Most of the time, the automatic dependency tracking in Visual Studio will handle changed files. But if there have been large changes, you may need to clean the installation. To do this, simply run the clean.bat command, which will automatically clean out all generated files. By default, all files are written into a subdirectory of the debug or release directories. To install these files using the standard layout, and also generate the files required to initialize and use the database, run the command: perl install.pl c:\destination\directory To run the regression tests, make sure you have completed the build of all required parts first. Also, make sure that the DLLs required to load all parts of the system (such as the Perl and Python DLLs for the procedural languages) are present in the system path. If they are not, set it through the buildenv.bat file. To run the tests, run one of the following commands from the src\tools\msvc directory: vcregress check vcregress installcheck vcregress plcheck vcregress contribcheck To change the schedule used (default is the parallel), append it to the command line like: vcregress check serial For more information about the regression tests, see . Building the PostgreSQL documentation in HTML format requires several tools and files. Create a root directory for all these files, and store them in the subdirectories in the list below. OpenJade 1.3.1-2 Download from and uncompress in the subdirectory openjade-1.3.1. DocBook DTD 4.2 Download from and uncompress in the subdirectory docbook. DocBook DSSSL 1.79 Download from and uncompress in the subdirectory docbook-dsssl-1.79. ISO character entities Download from and uncompress in the subdirectory docbook. Edit the buildenv.bat file, and add a variable for the location of the root directory, for example: @ECHO OFF SET DOCROOT=c:\docbook To build the documentation, run the command builddoc.bat. Note that this will actually run the build twice, in order to generate the indexes. The generated HTML files will be in doc\src\sgml. Using Visual C++ 7.1-8.0 or Borland C++ to build libpq is only recommended if you need a version with different debug/release flags, or if you need a static library to link into an application. For normal use the MinGW or Visual Studio 2005 version is recommended. To build the libpq client library using Visual Studio 7.1 or later, change into the src directory and type the command nmake /f win32.mak To build a 64-bit version of the libpq client library using Visual Studio 8.0 or later, change into the src directory and type in the command nmake /f win32.mak CPU=AMD64 See the win32.mak file for further details about supported variables. To build the libpq client library using Borland C++, change into the src directory and type the command make -N -DCFG=Release /f bcc32.mak The following files will be built: interfaces\libpq\Release\libpq.dll The dynamically linkable frontend library interfaces\libpq\Release\libpqdll.lib Import library to link your programs to libpq.dll interfaces\libpq\Release\libpq.lib Static version of the frontend library Normally you do not need to install any of the client files. You should place the libpq.dll file in the same directory as your applications executable file. Do not install libpq.dll into your Windows, System or System32 directory unless absolutely necessary. If this file is installed using a setup program, it should be installed with version checking using the VERSIONINFO resource included in the file, to ensure that a newer version of the library is not overwritten. If you are planning to do development using libpq on this machine, you will have to add the src\include and src\interfaces\libpq subdirectories of the source tree to the include path in your compiler's settings. To use the library, you must add the libpqdll.lib file to your project. (In Visual C++, just right-click on the project and choose to add it.)