UbuntuUpdates.org

Package "postgresql-13"

Name: postgresql-13

Description:

This package is just an umbrella for a group of other packages, it has no description.
Description samples from packages in group:

  • development files for PostgreSQL 13 server-side programming

Latest version: 13.7-0ubuntu0.21.10.1
Release: impish (21.10)
Level: updates
Repository: universe

Links



Other versions of "postgresql-13" in Impish

Repository Area Version
base main 13.4-1
base universe 13.4-1
security main 13.7-0ubuntu0.21.10.1
security universe 13.7-0ubuntu0.21.10.1
updates main 13.7-0ubuntu0.21.10.1
PPA: Postgresql 13.7-1.pgdg20.04+1
PPA: Postgresql 13.3-1.pgdg16.04+1
PPA: Postgresql 13.7-1.pgdg22.04+1
PPA: Postgresql 13.7-1.pgdg18.04+1

Packages in group

Deleted packages are displayed in grey.


Changelog

Version: 13.7-0ubuntu0.21.10.1 2022-05-24 17:06:25 UTC

  postgresql-13 (13.7-0ubuntu0.21.10.1) impish-security; urgency=medium

  * New upstream version (LP: #1973627).

    + A dump/restore is not required for those running 13.X.

    + However, if you have any GiST indexes on columns of type ltree (supplied
      by the contrib/ltree extension), you should re-index them after updating.
      See the upstream changelog linked below for further information.

    + Also, if you are upgrading from a version earlier than 13.6, see
      those release notes as well please.

    + Confine additional operations within "security restricted operation"
      sandboxes (Sergey Shinderuk, Noah Misch).

      Autovacuum, CLUSTER, CREATE INDEX, REINDEX, REFRESH MATERIALIZED VIEW,
      and pg_amcheck activated the "security restricted operation" protection
      mechanism too late, or even not at all in some code paths. A user having
      permission to create non-temporary objects within a database could
      define an object that would execute arbitrary SQL code with superuser
      permissions the next time that autovacuum processed the object, or that
      some superuser ran one of the affected commands against it.

      The PostgreSQL Project thanks Alexander Lakhin for reporting this
      problem.
      (CVE-2022-1552)

    + Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/13/release-13-7.html

 -- Athos Ribeiro <email address hidden> Tue, 17 May 2022 10:58:43 -0300

Source diff to previous version
1973627 New upstream microreleases 10.21, 12.11, 13.7 and 14.3

Version: 13.6-0ubuntu0.21.10.1 2022-03-16 02:06:20 UTC

  postgresql-13 (13.6-0ubuntu0.21.10.1) impish; urgency=medium

  * New upstream version (LP: #1961127).

    + A dump/restore is not required for those running 13.X.

    + However, if you have applied REINDEX CONCURRENTLY to a TOAST table's
      index, or observe failures to access TOAST datums, there has been a
      fix for this problem. Any existing corrupted indexes can be repaired
      by reindexing again.

    + Also, if you are upgrading from a version earlier than 13.5,
      see those release notes as well please.

    + Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/13/release-13-6.html

 -- Sergio Durigan Junior <email address hidden> Wed, 16 Feb 2022 21:17:27 -0500

Source diff to previous version
1961127 New upstream microreleases 10.20, 12.10, 13.6 and 14.2

Version: 13.5-0ubuntu0.21.10.1 2021-11-11 20:06:36 UTC

  postgresql-13 (13.5-0ubuntu0.21.10.1) impish-security; urgency=medium

  * New upstream version (LP: #1950268).

    + Make the server reject extraneous data after an SSL or GSS
      encryption handshake
      CVE-2021-23214

    + Make libpq reject extraneous data after an SSL or GSS
      encryption handshake
      CVE-2021-23222

    + A dump/restore is not required for those running 13.X.

    + However, note that installations using physical replication should
      update standby servers before the primary server, details in the
      release notes linked below.

    + Also, several bugs have been found that may have resulted in corrupted
      indexes, explained in detail in the release notes linked below. If any
      of those cases apply to you, it's recommended to reindex
      possibly-affected indexes after updating.

    + Also, if you are upgrading from a version earlier than 13.2,
      see those release notes as well please.

    + Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/13/release-13-5.html

 -- Christian Ehrhardt <email address hidden> Tue, 09 Nov 2021 09:46:55 +0100




About   -   Send Feedback to @ubuntu_updates