UbuntuUpdates.org

Package "postgresql-9.3"




Name: postgresql-9.3

Description:

object-relational SQL database, version 9.3 server

Latest version: *DELETED*
Release: trusty (14.04)
Level: proposed
Repository: main
Homepage: http://www.postgresql.org/

Links


Download "postgresql-9.3"


Other versions of "postgresql-9.3" in Trusty

Repository Area Version
base main 9.3.4-1
security main 9.3.24-0ubuntu0.14.04
updates main 9.3.24-0ubuntu0.14.04
PPA: Postgresql 9.3.6-1.pgdg10.4+1
PPA: Postgresql 9.3.17-1.pgdg12.4+1
PPA: Postgresql 9.3.25-1.pgdg14.04+1
PPA: Postgresql 9.3.25-3.pgdg16.04+1
PPA: Postgresql 9.3.25-8.pgdg18.04+1
PPA: Postgresql 9.3.25-9.pgdg20.04+3
PPA: Postgresql 9.3.25-9.pgdg22.04+3

Packages in group

Deleted packages are displayed in grey.


Changelog

Version: 9.3.17-0ubuntu0.14.04 2017-05-24 17:06:22 UTC

  postgresql-9.3 (9.3.17-0ubuntu0.14.04) trusty; urgency=medium

  * New upstream release (LP: #1690730)
    - Restrict visibility of pg_user_mappings.umoptions, to protect passwords
      stored as user mapping options (CVE-2017-7486)
    - Prevent exposure of statistical information via leaky operators
      (CVE-2017-7484)
    - Restore libpq's recognition of the PGREQUIRESSL environment variable
      (CVE-2017-7485)

    - A dump/restore is not required for those running 9.3.X.
    - However, if you use foreign data servers that make use of user passwords
      for authentication, see the first changelog entry.

    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.3/static/release-9-3-17.html

 -- Christian Ehrhardt <email address hidden> Mon, 15 May 2017 08:45:01 +0200

1690730 New upstream microreleases 9.3.17, 9.5.7 and 9.6.3
CVE-2017-7486 PostgreSQL versions 8.4 - 9.6 are vulnerable to information leak in pg_user_mappings view which discloses foreign server passwords to any user having
CVE-2017-7484 It was found that some selectivity estimation functions in PostgreSQL before 9.2.21, 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before 9.5.7, an
CVE-2017-7485 In PostgreSQL 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before 9.5.7, and 9.6.x before 9.6.3, it was found that the PGREQUIRESSL environment va

Version: *DELETED* 2017-02-20 20:07:13 UTC
No changelog for deleted or moved packages.

Version: 9.3.16-0ubuntu0.14.04 2017-02-15 14:06:56 UTC

  postgresql-9.3 (9.3.16-0ubuntu0.14.04) trusty; urgency=medium

  * New upstream release (LP: #1664478)
    - Fix a race condition that could cause indexes built with CREATE INDEX
      CONCURRENTLY to be corrupt (Pavan Deolasee, Tom Lane).
      If CREATE INDEX CONCURRENTLY was used to build an index that depends on
      a column not previously indexed, then rows inserted or updated by
      transactions that ran concurrently with the CREATE INDEX command could
      have received incorrect index entries. If you suspect this may have
      happened, the most reliable solution is to rebuild affected indexes
      after installing this update

    - Details about other changes:
      https://www.postgresql.org/docs/9.3/static/release-9-3-16.html

 -- Christian Ehrhardt <email address hidden> Tue, 14 Feb 2017 09:29:18 +0100

1664478 New upstream microreleases 9.3.16, 9.5.6

Version: *DELETED* 2016-11-06 08:06:46 UTC
No changelog for deleted or moved packages.

Version: 9.3.15-0ubuntu0.14.04 2016-10-28 00:07:16 UTC

  postgresql-9.3 (9.3.15-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1637236)
    - Fix WAL-logging of truncation of relation free space maps and visibility
      maps.
      It was possible for these files to not be correctly restored during
      crash recovery, or to be written incorrectly on a standby server. Bogus
      entries in a free space map could lead to attempts to access pages that
      have been truncated away from the relation itself, typically producing
      errors like "could not read block XXX: read only 0 of 8192 bytes".
      Checksum failures in the visibility map are also possible, if
      checksumming is enabled.

      Procedures for determining whether there is a problem and repairing it
      if so are discussed at
         https://wiki.postgresql.org/wiki/Free_Space_Map_Problems

    - Details about other changes:
      http://www.postgresql.org/docs/9.3/static/release-9-3-15.html

 -- Martin Pitt <email address hidden> Thu, 27 Oct 2016 21:20:52 +0200

1637236 New upstream microreleases 9.1.24, 9.3.15, 9.5.5



About   -   Send Feedback to @ubuntu_updates