Ubuntu

Bazaar branches of postgresql-9.1 in Ubuntu Precise

Name Status Last Modified Last Commit
lp:ubuntu/precise/postgresql-9.1 bug 2 Mature 2012-03-06 13:47:28 UTC 2012-03-06
20. * debian/control, debian/rules: Suppo...

Author: Martin Pitt
Revision Date: 2012-03-06 11:55:57 UTC

* debian/control, debian/rules: Support and prefer dpkg-buildflags when
  building with dpkg-dev >= 1.16.1~. Fall back to hardening-wrapper
  otherwise, to keep supporting backports.
* debian/rules: Build with "-z now" for some extra hardening. We can't use
  the full "hardening=+all", as PIE causes build failures.
* debian/copyright: Fix syntax for copyright format 1.0.
* debian/control: Bump Breaks/Replaces versions to current binary version,
  so that e. g. the moved pg_basebackup does not cause upgrade errors when
  upgrading from higher point releases in previous distro releases.
  (LP: #944632)

lp:ubuntu/precise-proposed/postgresql-9.1 bug 2 Mature 2012-12-10 14:54:49 UTC 2012-12-10
25. * New upstream bug fix release: (LP: ...

Author: Martin Pitt
Revision Date: 2012-12-10 14:54:49 UTC

* New upstream bug fix release: (LP: #1088393)
  - Fix multiple bugs associated with "CREATE INDEX CONCURRENTLY".
    Fix "CREATE INDEX CONCURRENTLY" to use in-place updates when
    changing the state of an index's pg_index row. This prevents race
    conditions that could cause concurrent sessions to miss updating
    the target index, thus resulting in corrupt concurrently-created
    indexes.
    Also, fix various other operations to ensure that they ignore
    invalid indexes resulting from a failed "CREATE INDEX CONCURRENTLY"
    command. The most important of these is "VACUUM", because an
    auto-vacuum could easily be launched on the table before corrective
    action can be taken to fix or remove the invalid index.
  - Fix buffer locking during WAL replay.
    The WAL replay code was insufficiently careful about locking
    buffers when replaying WAL records that affect more than one page.
    This could result in hot standby queries transiently seeing
    inconsistent states, resulting in wrong answers or unexpected
    failures.
  - See HISTORY/changelog.gz for the other bug fixes.
* Drop 00git_ecpg_array_bounds.patch, fixed upstream.

lp:ubuntu/precise-security/postgresql-9.1 bug 2 Mature 2013-05-04 07:03:46 UTC 2013-05-04
24. * New upstream security/bug fix relea...

Author: Martin Pitt
Revision Date: 2013-04-02 11:59:41 UTC

* New upstream security/bug fix release: (LP: #1163184)
  - Fix insecure parsing of server command-line switches.
    A connection request containing a database name that begins with
    "-" could be crafted to damage or destroy files within the server's
    data directory, even if the request is eventually rejected.
    [CVE-2013-1899]
  - Reset OpenSSL randomness state in each postmaster child process.
    This avoids a scenario wherein random numbers generated by
    "contrib/pgcrypto" functions might be relatively easy for another
    database user to guess. The risk is only significant when the
    postmaster is configured with ssl = on but most connections don't
    use SSL encryption. [CVE-2013-1900]
  - Make REPLICATION privilege checks test current user not
    authenticated user.
    An unprivileged database user could exploit this mistake to call
    pg_start_backup() or pg_stop_backup(), thus possibly interfering
    with creation of routine backups. [CVE-2013-1901]
  - Fix GiST indexes to not use "fuzzy" geometric comparisons when it's
    not appropriate to do so.
    The core geometric types perform comparisons using "fuzzy"
    equality, but gist_box_same must do exact comparisons, else GiST
    indexes using it might become inconsistent. After installing this
    update, users should "REINDEX" any GiST indexes on box, polygon,
    circle, or point columns, since all of these use gist_box_same.
  - Fix erroneous range-union and penalty logic in GiST indexes that
    use "contrib/btree_gist" for variable-width data types, that is
    text, bytea, bit, and numeric columns.
    These errors could result in inconsistent indexes in which some
    keys that are present would not be found by searches, and also in
    useless index bloat. Users are advised to "REINDEX" such indexes
    after installing this update.
  - Fix bugs in GiST page splitting code for multi-column indexes.
    These errors could result in inconsistent indexes in which some
    keys that are present would not be found by searches, and also in
    indexes that are unnecessarily inefficient to search. Users are
    advised to "REINDEX" multi-column GiST indexes after installing
    this update.
  - See HISTORY/changelog.gz for details about the other bug fixes.

lp:ubuntu/precise-updates/postgresql-9.1 2 Mature 2013-04-02 11:59:41 UTC 2013-04-02
24. * New upstream security/bug fix relea...

Author: Martin Pitt
Revision Date: 2013-04-02 11:59:41 UTC

* New upstream security/bug fix release: (LP: #1163184)
  - Fix insecure parsing of server command-line switches.
    A connection request containing a database name that begins with
    "-" could be crafted to damage or destroy files within the server's
    data directory, even if the request is eventually rejected.
    [CVE-2013-1899]
  - Reset OpenSSL randomness state in each postmaster child process.
    This avoids a scenario wherein random numbers generated by
    "contrib/pgcrypto" functions might be relatively easy for another
    database user to guess. The risk is only significant when the
    postmaster is configured with ssl = on but most connections don't
    use SSL encryption. [CVE-2013-1900]
  - Make REPLICATION privilege checks test current user not
    authenticated user.
    An unprivileged database user could exploit this mistake to call
    pg_start_backup() or pg_stop_backup(), thus possibly interfering
    with creation of routine backups. [CVE-2013-1901]
  - Fix GiST indexes to not use "fuzzy" geometric comparisons when it's
    not appropriate to do so.
    The core geometric types perform comparisons using "fuzzy"
    equality, but gist_box_same must do exact comparisons, else GiST
    indexes using it might become inconsistent. After installing this
    update, users should "REINDEX" any GiST indexes on box, polygon,
    circle, or point columns, since all of these use gist_box_same.
  - Fix erroneous range-union and penalty logic in GiST indexes that
    use "contrib/btree_gist" for variable-width data types, that is
    text, bytea, bit, and numeric columns.
    These errors could result in inconsistent indexes in which some
    keys that are present would not be found by searches, and also in
    useless index bloat. Users are advised to "REINDEX" such indexes
    after installing this update.
  - Fix bugs in GiST page splitting code for multi-column indexes.
    These errors could result in inconsistent indexes in which some
    keys that are present would not be found by searches, and also in
    indexes that are unnecessarily inefficient to search. Users are
    advised to "REINDEX" multi-column GiST indexes after installing
    this update.
  - See HISTORY/changelog.gz for details about the other bug fixes.

14 of 4 results