Ubuntu
postgresql-10 package

~paelzer/ubuntu/+source/postgresql-10:MRE-1833211-june2019-bionic

  1. Git
  2. lp:~paelzer/ubuntu/+source/postgresql-10
  3. MRE-1833211-june2019-bionic
Last commit made on 2019-06-18
Get this branch:
git clone -b MRE-1833211-june2019-bionic https://git.launchpad.net/~paelzer/ubuntu/+source/postgresql-10
Only Christian Ehrhardt  can upload to this branch. If you are Christian Ehrhardt  please log in for upload directions.

Branch merges

Branch information

Name:
MRE-1833211-june2019-bionic
Repository:
lp:~paelzer/ubuntu/+source/postgresql-10

Recent commits

50d431e... by Christian Ehrhardt 

changelog: Upstream release 10.9

Signed-off-by: Christian Ehrhardt <email address hidden>

03a2977... by Christian Ehrhardt 

New Upstream release 10.9

Signed-off-by: Christian Ehrhardt <email address hidden>

c7e5344... by Christian Ehrhardt 

Import patches-unapplied version 10.8-0ubuntu0.18.04.1 to ubuntu/bionic-security

Imported using git-ubuntu import.

Changelog parent: a9dfb6adbf8500038757cfc3e3bbdc6d750b4584

New changelog entries:
  * New upstream release(s) (LP: #1828012)
    - Prevent row-level security policies from being bypassed via
      selectivity estimators.
      CVE-2019-10130
    - Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/10/static/release-10-8.html

a9dfb6a... by Christian Ehrhardt 

Import patches-unapplied version 10.7-0ubuntu0.18.04.1 to ubuntu/bionic-proposed

Imported using git-ubuntu import.

Changelog parent: 5b7ec653ff42b9f457de1b2349cd67d0693bbd22

New changelog entries:
  * New upstream release (LP: #1815665)
    - By default, panic instead of retrying after fsync() failure, to avoid
      possible data corruption. A new server parameter "guc-data-sync-retry"
      has been added to control this;
    - d/p/pg-10-Disallow-setting-client_min_messages-higher-than-ERR.patch:
      to retain SRU stability this patch reverts one of the changes which
      disabled the error suppression by setting client_min_messages to
      fatal or panic. Overall that means no change to the handling of
      client_min_messages due to this upload.
    - d/p/pg-10-Rename-rbtree.c-functions-to-use-rbt-prefix-not-rb-p.patch:
      this change of 10.7 would break an external ABI/API exposed to
      extensions. To avoid breaking those (especially those not in the Ubuntu
      Archive that we can't control) this change of upstreams stable release
      is reverted. Thereby the ABI/API is unchanged in regard to the rb_
      function prefix by this new package upload to Ubuntu.
    - Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/10/static/release-10-7.html

5b7ec65... by Marc Deslauriers

Import patches-unapplied version 10.6-0ubuntu0.18.04.1 to ubuntu/bionic-security

Imported using git-ubuntu import.

Changelog parent: 37ba6a2e2ea5dac5162d528a2a321c65ac85b6e8

New changelog entries:
  * SECURITY UPDATE: Updated to 10.6 to fix security issue.
    - Details about the new release can be found at
      https://www.postgresql.org/docs/10/release-10-6.html
    - CVE-2018-16850

37ba6a2... by Christian Ehrhardt 

Import patches-unapplied version 10.5-0ubuntu0.18.04 to ubuntu/bionic-security

Imported using git-ubuntu import.

Changelog parent: 46ccc300b2da15db99d724eb7149ab74fdb752c7

New changelog entries:
  * New upstream release (LP: #1786938)
    - Fix failure to reset libpq's state fully between connection attempts
      .
      An unprivileged user of dblink or postgres_fdw could bypass the checks
      intended to prevent use of server-side credentials, such as a ~/.pgpass
      file owned by the operating-system user running the server. Servers
      allowing peer authentication on local connections are particularly
      vulnerable. Other attacks such as SQL injection into a postgres_fdw
      session are also possible. Attacking postgres_fdw in this way requires
      the ability to create a foreign server object with selected connection
      parameters, but any user with access to dblink could exploit the
      problem. In general, an attacker with the ability to select the
      connection parameters for a libpq-using application could cause
      mischief, though other plausible attack scenarios are harder to think
      of. Our thanks to Andrew Krasichkov for reporting this issue.
      (CVE-2018-10915)
    - Fix INSERT ... ON CONFLICT UPDATE through a view that isn't just SELECT
      FROM ...
      .
      Erroneous expansion of an updatable view could lead to crashes or
      attribute ... has the wrong type errors, if the view's SELECT list
      doesn't match one-to-one with the underlying table's columns.
      Furthermore, this bug could be leveraged to allow updates of columns
      that an attacking user lacks UPDATE privilege for, if that user has
      INSERT and UPDATE privileges for some other column(s) of the table. Any
      user could also use it for disclosure of server memory.
      (CVE-2018-10925)
    - d/libecpg-dev.install: Add new pgtypes header.
    - d/libpgtypes3.symbols: Add new pgtypes symbol.
    - d/p/filter-debug-prefix-map: update to match 10.5
    - update maintainers
    - Details about these and other changes can be found at
      https://www.postgresql.org/docs/10/static/release-10-5.html

46ccc30... by Christian Ehrhardt 

Import patches-unapplied version 10.4-0ubuntu0.18.04 to ubuntu/bionic-proposed

Imported using git-ubuntu import.

Changelog parent: 3c97ca8118bb28a6d31782c67cbee3761fe558d5

New changelog entries:
  * New upstream release (LP: #1769888)
    - A dump/restore is not required for those running 10.X.
      However, if you use the adminpack extension, you should update it as
      per the first changelog entry of the changelog.
      (CVE-2018-1115)
      Also, if the function marking mistakes mentioned in the first
      changelog entry affect you, you will want to take steps to
      correct your database catalogs.
    - Details about changes can be found at
      https://www.postgresql.org/docs/10/static/release-10-4.html

3c97ca8... by Christoph Berg <email address hidden>

Import patches-unapplied version 10.3-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 08309b1755673fee6be5f3ab76ac7bc831579a48

New changelog entries:
  * New upstream version.
    If you run an installation in which not all users are mutually
    trusting, or if you maintain an application or extension that is
    intended for use in arbitrary situations, it is strongly recommended
    that you read the documentation changes described in the first changelog
    entry below, and take suitable steps to ensure that your installation or
    code is secure.
    Also, the changes described in the second changelog entry below may
    cause functions used in index expressions or materialized views to fail
    during auto-analyze, or when reloading from a dump. After upgrading,
    monitor the server logs for such problems, and fix affected functions.
    + Document how to configure installations and applications to guard
      against search-path-dependent trojan-horse attacks from other users
      Using a search_path setting that includes any schemas writable by a
      hostile user enables that user to capture control of queries and then
      run arbitrary SQL code with the permissions of the attacked user. While
      it is possible to write queries that are proof against such hijacking,
      it is notationally tedious, and it's very easy to overlook holes.
      Therefore, we now recommend configurations in which no untrusted schemas
      appear in one's search path.
      (CVE-2018-1058)
    + Avoid use of insecure search_path settings in pg_dump and other client
      programs
      pg_dump, pg_upgrade, vacuumdb and other PostgreSQL-provided applications
      were themselves vulnerable to the type of hijacking described in the
      previous changelog entry; since these applications are commonly run by
      superusers, they present particularly attractive targets. To make them
      secure whether or not the installation as a whole has been secured,
      modify them to include only the pg_catalog schema in their search_path
      settings. Autovacuum worker processes now do the same, as well.
      In cases where user-provided functions are indirectly executed by these
      programs -- for example, user-provided functions in index expressions --
      the tighter search_path may result in errors, which will need to be
      corrected by adjusting those user-provided functions to not assume
      anything about what search path they are invoked under. That has always
      been good practice, but now it will be necessary for correct behavior.
      (CVE-2018-1058)

08309b1... by Christoph Berg <email address hidden>

Import patches-unapplied version 10.2-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: bf4c60a3e4602e70ecd9a84f257196b17e5a232b

New changelog entries:
  * New upstream version.
    + Fix processing of partition keys containing multiple expressions
      (CVE-2018-1052)
    + Ensure that all temporary files made by pg_upgrade are
      non-world-readable (CVE-2018-1053)
    + Change the behavior of contrib/cube's cube ~> int operator to make it
      compatible with KNN search.
      The meaning of the second argument (the dimension selector) has been
      changed to make it predictable which value is selected even when
      dealing with cubes of varying dimensionalities.
      This is an incompatible change, but since the point of the operator
      was to be used in KNN searches, it seems rather useless as-is.
      After installing this update, any expression indexes or materialized
      views using this operator will need to be reindexed/refreshed.

bf4c60a... by Christoph Berg <email address hidden>

Import patches-unapplied version 10.1-3 to debian/sid

Imported using git-ubuntu import.

Changelog parent: bc6023320e84e7cbcc26824828d83714ccbf5a55

New changelog entries:
  * Suppress build variability in schemapg.h.
  * Include package version number in "extra version" so it is reported by
    "psql --version" and friends.
  * postgresql-10.postinst: Ignore command-with-path-in-maintainer-script.
  * debian/rules: Set DEB_HOST_* via /usr/share/dpkg/architecture.mk.