lp:debian/stretch/postgresql-9.6

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

11. By Christoph Berg <email address hidden> on 2016-11-02

* Team upload.

[ Martin Pitt ]
* Add missing perl test dependency (for Test::More).

[ Christoph Berg ]
* Explicitly disable PIE on 32 architectures. Previously we were just not
  enabling it, but it's on by default now in unstable. Closes: #842752.
* libpq-dev: Remove dependency on libssl-dev (and comerr-dev and
  krb5-multidev) to unbreak co-installation with libssl1.0-dev.

10. By Christoph Berg on 2016-10-25

* New upstream release.

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

  However, if your installation has been affected by the bugs described in
  the first two changelog entries below, then after updating you may need
  to take action to repair corrupted free space maps and/or visibility
  maps.

  + Fix WAL-logging of truncation of relation free space maps and visibility
    maps (Pavan Deolasee, Heikki Linnakangas)

    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.

  + Fix possible data corruption when pg_upgrade rewrites a relation
    visibility map into 9.6 format (Tom Lane)

    On big-endian machines, bytes of the new visibility map were written in
    the wrong order, leading to a completely incorrect map. On Windows, the
    old map was read using text mode, leading to incorrect results if the
    map happened to contain consecutive bytes that matched a carriage
    return/line feed sequence. The latter error would almost always lead to
    a pg_upgrade failure due to the map file appearing to be the wrong
    length.

    If you are using a big-endian machine (many non-Intel architectures are
    big-endian) and have used pg_upgrade to upgrade from a pre-9.6 release,
    you should assume that all visibility maps are incorrect and need to be
    regenerated. It is sufficient to truncate each relation's visibility
    map with contrib/pg_visibility's pg_truncate_visibility_map() function.
    For more information see
    https://wiki.postgresql.org/wiki/Visibility_Map_Problems.

9. By Christoph Berg <email address hidden> on 2016-09-27

* First 9.6 release.
* Filter -fdebug-prefix-map from pg_config output. This makes the build
  reproducible; the flag would be useless anyway.
* Drop hardening-wrapper.

8. By Christoph Berg on 2016-08-29

First 9.6 release candidate.

7. By Christoph Berg <email address hidden> on 2016-08-09

New upstream beta version.

6. By Christoph Berg on 2016-07-19

* New upstream beta version.
* Simplify python3 rules, upstream implemented the necessary dependencies.

5. By Christoph Berg on 2016-06-20

* New upstream beta version.
* Run regression tests in architecture-dependant builds only.
* Remove conditional multi-arch compilation, all supported dists are
  multi-arched now.
* Use explicit xz compression for wheezy and precise

4. By Christoph Berg <email address hidden> on 2016-05-18

Split the build process into indep and arch parts. (The manpages are still
built in both because they are distributed over the server and doc
packages.)

3. By Christoph Berg <email address hidden> on 2016-05-17

* Use dh-exec to not install the sepgsql files on non-linux.
* B-D on libsystemd-dev on linux only.

2. By Christoph Berg on 2016-05-13

Merge back separate contrib copyright file into debian/copyright.