A powerful, open source relational database system

PostgreSQL

Join our mailing list

Stay up to date with latest software releases, news, software discounts, deals and more.

Subscribe

PostgreSQL 11.12

  -  267 MB  -  Open Source

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system. Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of PostgreSQL 11.12.


For those interested in downloading the most recent release of PostgreSQL or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • PostgreSQL 11.12 Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    PostgreSQL 11.12 Screenshot 1
  • PostgreSQL 11.12 Screenshot 2
  • PostgreSQL 11.12 Screenshot 3
  • PostgreSQL 11.12 Screenshot 4
  • PostgreSQL 11.12 Screenshot 5

What's new in this version:

Security Issues:
CVE-2021-32027: Buffer overrun from integer overflow in array subscripting calculations:
- Versions Affected: 9.6 - 13. The security team typically does not test unsupported versions, but this problem is quite old
- While modifying certain SQL array values, missing bounds checks let authenticated database users write arbitrary bytes to a wide area of server memory
- The PostgreSQL project thanks Tom Lane for reporting this problem

CVE-2021-32028: Memory disclosure in INSERT ... ON CONFLICT ... DO UPDATE:
- Versions Affected: 9.6 - 13. The security team typically does not test unsupported versions. The feature first appeared in 9.5
- Using an INSERT ... ON CONFLICT ... DO UPDATE command on a purpose-crafted table, an attacker can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can create prerequisite objects and complete this attack at will. A user lacking the CREATE and TEMPORARY privileges on all databases and the CREATE privilege on all schemas cannot use this attack at will.
- The PostgreSQL project thanks Andres Freund for reporting this problem

CVE-2021-32029: Memory disclosure in partitioned-table UPDATE ... RETURNING:
- Versions Affected: 11 - 13
- Using an UPDATE ... RETURNING on a purpose-crafted partitioned table, an attacker can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can create prerequisite objects and complete this attack at will. A user lacking the CREATE and TEMPORARY privileges on all databases and the CREATE privilege on all schemas typically cannot use this attack at will.

Bug Fixes and Improvements:
- This update fixes over 45 bugs that were reported in the last several months. Some of these issues only affect version 13, but could also apply to other supported versions.

Some of these fixes include:
- Fix potential incorrect computation of UPDATE ... RETURNING outputs for joined, cross-partition updates
- Fix ALTER TABLE ... ALTER CONSTRAINT when used on foreign-key constraints on partitioned tables. The command would fail to adjust the DEFERRABLE and/or INITIALLY DEFERRED properties of the constraints and triggers of leaf partitions, leading to unexpected behavior. After updating to this version, you can execute the ALTER TABLE ... ALTER CONSTRAINT command to fix any misbehaving partitioned tables.
- Ensure that when a child table is attached with ALTER TABLE ... INHERIT that generated columns in the parent are generated in the same way in the child
- Forbid marking an identity column as NULL
- Allow ALTER ROLE ... SET/ALTER DATABASE ... SET to set the role, session_authorization, and temp_buffers parameters
- Ensure that REINDEX CONCURRENTLY preserves any statistics target set for the index
- Fix an issue where, in some cases, saving records within AFTER triggers could cause crashes
- Fix how to_char() handles Roman-numeral month format codes with negative intervals
- Fix use of uninitialized value while parsing an {m,n} quantifier in a BRE-mode regular expression
- Fix "could not find pathkey item to sort" planner errors that occur in some situations when the sort key involves an aggregate or window function
- Fix issue with BRIN index bitmap scans that could lead to "could not open file" errors
- Fix potentially wrong answers from GIN tsvector index searches when there are many matching records
- Fixes for COMMIT AND CHAIN functionality on both the server and psql
- Avoid incorrect timeline change while recovering uncommitted two-phase transactions from WAL, which could lead to consistency issues and the inability to restart the server.
- Ensure thatwal_sync_method is set to fdatasync by default on newer FreeBSD releases
- Disable the vacuum_cleanup_index_scale_factor parameter and storage option
- Fix several memory leaks in the server, including one with SSL/TLS parameter initialization
- Restore the previous behavior of connect service=XYZ to psql, i.e. disallow environmental variables (e.g. PGPORT) from overriding entries in the service file
- Fix how pg_dump handles generated columns in partitioned tables
- Add additional checks to pg_upgrade for user tables containing non-upgradable data types
- On Windows, initdb now prints instructions about how to start the server with pg_ctl using backslash separators
- Fix pg_waldump to count XACT records correctly when generating per-record statistics

Join our mailing list

Stay up to date with latest software releases, news, software discounts, deals and more.

Subscribe