Branches for Hardy

Author: Martin Pitt
Revision Date: 2008-03-31 11:32:39 UTC

* Urgency medium since #472930 is an important bug fix.
* debian/init.d-functions: If there are no clusters, exit with 4 (LSB-code
  for "unknown status") instead of 0 (which means "service is running", but
  it is debatable and confusing whether all clusters are running if there
  are none at all). (LP: #203966)
* Update Spanish debconf translations, thanks Javier Fernández-Sanguino
  Peña. (Closes: #473405)
* t/060_obsolete_confparams.t: Run upgrades under
  default_transaction_read_only=on. t/040_upgrade.t still uses the default
  "off", so both cases get tested. This replicates the problem report from
  Karsten Hilbert.
* pg_upgradecluster: Work with default_transaction_read_only=on.
* debian/autovacuum.conf, architecture.html: Point out that this file is
  only relevant for PostgreSQL versions earlier than 8.1. Thanks to Ross
  Boylan for pointing this out.
* Add t/051_inconsistent_encoding_upgrade.t: Check that upgrades from
  pre-8.3 to 8.3 succeed and have correct encodings if the old DB had a
  database whose encoding did not match the server locale. This reproduces
  #472930.
* pg_upgradecluster: Fix handling of database encodings on upgrade, since
  8.3 now forces DB encodings and server locale to match:
  - With C locale, keep encoding of DBs on upgrade, just as in previous
    versions. (C is compatible with all encodings, and causes lots of string
    functions not to work correctly, but people still use it deliberately.)
  - With other locales, create the target DB manually with a compatible
    encoding, and call pg_restore in a way to not create the target DB and
    automatically convert encoding.
  - Closes: #472930, LP: #207779

Author: Martin Pitt
Revision Date: 2011-01-03 10:16:55 UTC

Backport current version to hardy, as the current postgresql-8.4 backport
needs this newer version. Drop debian/source/format, as hardy does not yet
support 3.0 sources. (LP: #693157)

Author: Martin Pitt
Revision Date: 2010-10-18 11:09:35 UTC

* t/030_errors.t: Check that pg_createcluster leaves the original one
  intact if the cluster already exists, also when the original one is not
  running. This reproduces LP #661061/Debian #597097.
* pg_createcluster: Be more careful with cleaning up the created cluster if
  an error occurs: Do not start the cleanup until we actually passed our
  sanity checks and created files for the new cluster. Before, it would
  erroneously remove an already existing cluster on a sanity check fail, if
  that cluster happened to not be running at the time. (LP: #661061)
  Patches cherrypicked from trunk r1024.

Author: Martin Pitt
Revision Date: 2010-10-18 11:09:35 UTC

* t/030_errors.t: Check that pg_createcluster leaves the original one
  intact if the cluster already exists, also when the original one is not
  running. This reproduces LP #661061/Debian #597097.
* pg_createcluster: Be more careful with cleaning up the created cluster if
  an error occurs: Do not start the cleanup until we actually passed our
  sanity checks and created files for the new cluster. Before, it would
  erroneously remove an already existing cluster on a sanity check fail, if
  that cluster happened to not be running at the time. (LP: #661061)
  Patches cherrypicked from trunk r1024.