PostgreSQL 9.1.3-1 freeware    

Author PostgreSQL Global Development OS Windows2000, Windows2003, WinXP, Windows Vista, Windows Vista x64, Windows 7, Windows 7 x64, Linux, Mac OS X Date Released February 27, 2012 Downloads 1245 Filesize 46.00 MB Keywords relational database, database manager, query planner, relational, database, manager, Postgre SQL Your Rating   - click to rate - you will be first!

[ View full size screenshot ]

Download PostgreSQL   Save Freeware   Report Spyware

PostgreSQL has more than 15 years of active development and a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness.

PostgreSQL runs on all major operating systems, including Linux, UNIX (AIX, BSD, HP-UX, SGI IRIX, Mac OS X, Solaris, Tru64), and Windows. ...

Download PostgreSQL   Save Freeware   Report Spyware

Far manager - PostgreSQL freeware - Download Notice

PostgreSQL Free Download - we do not host any PostgreSQL torrent files or links of PostgreSQL on rapidshare.com, depositfiles.com, megaupload.com etc. All PostgreSQL download links are direct PostgreSQL full download from publisher site or their selected mirrors.

Far manager - PostgreSQL freeware - Latest User Reviews

 Write a Review   

Far manager - PostgreSQL freeware - The Latest Versions History

Version	Date Released	Status	Release Notes
9.1.3-1	Feb 27, 2012	New Release	#Require execute permission on the trigger function for CREATE TRIGGER (Robert Haas) This missing check could allow another user to execute a trigger function with forged input data, by installing it on a table he owns. This is only of significance for trigger functions marked SECURITY DEFINER, since otherwise trigger functions run as the table owner anyway. (CVE-2012-0866) #Remove arbitrary limitation on length of common name in SSL certificates (Heikki Linnakangas) Both libpq and the server truncated the common name extracted from an SSL certificate at 32 bytes. Normally this would cause nothing worse than an unexpected verification failure, but there are some rather-implausible scenarios in which it might allow one certificate holder to impersonate another. The victim would have to have a common name exactly 32 bytes long, and the attacker would have to persuade a trusted CA to issue a certificate in which the common name has that string as a prefix.
9.1.2-1	Dec 6, 2011	New Release	· Fix bugs in information_schema.referential_constraints view (Tom Lane). This view was being insufficiently careful about matching the foreign-key constraint to the depended-on primary or unique key constraint. That could result in failure to show a foreign key constraint at all, or showing it multiple times, or claiming that it depends on a different constraint than the one it really does. Since the view definition is installed by initdb, merely upgrading will not fix the problem. If you need to fix this in an existing installation, you can (as a superuser) drop the information_schema schema then re-create it by sourcing SHAREDIR/information_schema.sql. (Run pg_config --sharedir if you're uncertain where SHAREDIR is.) This must be repeated in each database to be fixed. · Make contrib/citext's upgrade script fix collations of citext columns and indexes (Tom Lane). Existing citext columns.
9.1.1-1	Sep 26, 2011	New Release	· Make pg_options_to_table return NULL for an option with no value · Previously such cases would result in a server crash. · Fix memory leak at end of a GiST index scan · Commands that perform many separate GiST index scans, such as verification of a new GiST-based exclusion constraint on a table already containing many rows, could transiently require large amounts of memory due to this leak. · Fix explicit reference to pg_temp schema in CREATE TEMPORARY TABLE
9.1.0-1	Sep 13, 2011	New Release	· Allow synchronous replication · Add support for foreign tables · Add per-column collation support · Add extensions which simplify packaging of additions to PostgreSQL · Add a true serializable isolation level · Support unlogged tables using the UNLOGGED option in CREATE TABLE · Allow data-modification commands (INSERT/UPDATE/DELETE) in WITH clauses · Add nearest-neighbor (order-by-operator) searching to GiST indexes · Add a SECURITY LABEL command and support for SELinux permissions control · Update the PL/Python server-side language
9.0.4-1	Apr 18, 2011	New Release	Changes: · Force the default wal_sync_method to be fdatasync on Linux (Tom Lane, Marti Raudsepp) · The default on Linux has actually been fdatasync for many years, but recent kernel changes caused PostgreSQL to choose open_datasync instead. This choice did not result in any performance improvement, and caused outright failures on certain filesystems, notably ext4 with the data=journal mount option. · Fix "too many KnownAssignedXids" error during Hot Standby replay (Heikki Linnakangas) · Fix race condition in lock acquisition during Hot Standby (Simon Riggs) · Avoid unnecessary conflicts during Hot Standby (Simon Riggs) · This fixes some cases where replay was considered to conflict with standby queries (causing delay of replay or possibly cancellation of the queries), but there was no real conflict. · Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane) · This could result in "bad buffer id: 0" failures or corruption of index contents during replication.
9.0.3-1	Jan 31, 2011	New Release	Changes: · Force the default wal_sync_method to be fdatasync on Linux (Tom Lane, Marti Raudsepp) · The default on Linux has actually been fdatasync for many years, but recent kernel changes caused PostgreSQL to choose open_datasync instead. This choice did not result in any performance improvement, and caused outright failures on certain filesystems, notably ext4 with the data=journal mount option. · Fix "too many KnownAssignedXids" error during Hot Standby replay (Heikki Linnakangas) · Fix race condition in lock acquisition during Hot Standby (Simon Riggs) · Avoid unnecessary conflicts during Hot Standby (Simon Riggs) · This fixes some cases where replay was considered to conflict with standby queries (causing delay of replay or possibly cancellation of the queries), but there was no real conflict. · Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane) · This could result in "bad buffer id: 0" failures or corruption of index contents during replication.
9.0.2-1	Dec 18, 2010	New Release	Changes: · Force the default wal_sync_method to be fdatasync on Linux (Tom Lane, Marti Raudsepp) · The default on Linux has actually been fdatasync for many years, but recent kernel changes caused PostgreSQL to choose open_datasync instead. This choice did not result in any performance improvement, and caused outright failures on certain filesystems, notably ext4 with the data=journal mount option. · Fix "too many KnownAssignedXids" error during Hot Standby replay (Heikki Linnakangas) · Fix race condition in lock acquisition during Hot Standby (Simon Riggs) · Avoid unnecessary conflicts during Hot Standby (Simon Riggs) · This fixes some cases where replay was considered to conflict with standby queries (causing delay of replay or possibly cancellation of the queries), but there was no real conflict. · Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane) · This could result in "bad buffer id: 0" failures or corruption of index contents during replication.
9.0.1-1	Oct 4, 2010	New Release	Use a separate interpreter for each calling SQL userid in PL/Perl and PL/Tcl: · This change prevents security problems that can be caused by subverting Perl or Tcl code that will be executed later in the same session under another SQL user identity (for example, within a SECURITY DEFINER function). Most scripting languages offer numerous ways that that might be done, such as redefining standard functions or operators called by the target function. Without this change, any SQL user with Perl or Tcl language usage rights can do essentially anything with the SQL privileges of the target function's owner. · The cost of this change is that intentional communication among Perl and Tcl functions becomes more difficult. To provide an escape hatch, PL/PerlU and PL/TclU functions continue to use only one interpreter per session. This is not considered a security issue since all such functions execute at the trust level of a database superuser already.
8.4.4-1	May 17, 2010	New Release	· Add new configuration parameter ssl_renegotiation_limit to control how often we do session key renegotiation for an SSL connection (Magnus) · This can be set to zero to disable renegotiation completely, which may be required if a broken SSL library is used. In particular, some vendors are shipping stopgap patches for CVE-2009-3555 that cause renegotiation attempts to fail. · Fix possible deadlock during backend startup (Tom) · Fix possible crashes due to not handling errors during relcache reload cleanly (Tom) · Fix possible crash due to use of dangling pointer to a cached plan (Tatsuo) · Fix possible crash due to overenthusiastic invalidation of cached plan for ROLLBACK (Tom) · Fix possible crashes when trying to recover from a failure in subtransaction start (Tom) · Fix server memory leak associated with use of savepoints and a client encoding different from server's encoding (Tom)
8.4.3-1	Apr 27, 2010	New Release	#Add new configuration parameter ssl_renegotiation_limit to control how often we do session key renegotiation for an SSL connection (Magnus) This can be set to zero to disable renegotiation completely, which may be required if a broken SSL library is used. In particular, some vendors are shipping stopgap patches for CVE-2009-3555 that cause renegotiation attempts to fail. #Fix possible deadlock during backend startup (Tom) #Fix possible crashes due to not handling errors during relcache reload cleanly (Tom) #Fix possible crash due to use of dangling pointer to a cached plan (Tatsuo) #Fix possible crash due to overenthusiastic invalidation of cached plan for ROLLBACK (Tom) #Fix possible crashes when trying to recover from a failure in subtransaction start (Tom) #Fix server memory leak associated with use of savepoints and a client encoding different from server's encoding (Tom)