Hopefully, this release will be a little smoother than the last one was. For this release, we have 3 download locations and servers. The SourceForge.net download went up first, and appears to be downloading correctly. We don't think we'll get the file corruption issues we had with 8.3.0, but only time will tell. Second, we've placed another download location on the Druware Software Designs pipeline. Third, we are hosting a download location on the PostgreSQLforMac host, which actually has the worst bandwidth of the three.
PostgreSQL 8.3.1 - Universal Build
Release Notes and Quick Installation Guide
Release Notes
This release contains some of the latest released code from the PostgreSQL project.
01-April-2008
Tweaked x86_64 settings for better compatabliity
Reworked installer scripts to better handle errors and permissions
Updated to PostgreSQL 8.3.1
Added Auotmator Actions from Druware
Installation Guide
This package contains three separate and distinct installers. One for the server, one for the client tools and one for the developer. All three can be installed side by side. The Server portion is a .pkg installer. The Server installation goes into the /Library/ folder. It will install into two folders, /Library/PostgreSQL8 and /Library/StartupItems/PostgreSQL. It also creates a Postgres user and group via the Directory Services command line. There is an uninstall script placed into the /Library/PostgreSQL8 folder that removes all of the above. The server installation does not include the static libraries, only the dynamic libraries. If you want the static libraries, you will need to unpack the /opt/ folder from the Developer folder into the / folder of the boot disk.
The Developer folder contains a zip of the /opt/local tree with headers and static libraries that should be unzipped into the root of the boot drive, in keeping with traditional Unix paths. This is not configured to be run, and is intended to be used primarily by developers that wish to compile against the static libraries. One of the oddities of using Xcode is that if the equivalent .dylib exists in the same path as the referenced .a, it will link against the .dylib. Annoying, but the workaround is to put the .a’s somewhere else, and this is our solution. Also in the Developer folder are binaries of the embeddable PGSQLKit.framework, the pgCocoaDB.framework, as these are tools for the developer to build their own Cocoa based applications for PostgreSQL.
The Client Tools package is no longer a .pkg installer, though the .pkg does remain in the server install package, and can be run on it’s own. Since it does not need to place anything in specific locations, all of the Client tool applications have been placed in a folder, so that you may elect what you wish to put where. Further, these tools can be installed to any Mac OS X (10.4.4+) install and do not require a local installation of the server.