Debian Bug report logs - #700271
mention database encoding used during installation

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Helmut Grohne <helmut@subdivi.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: postgresql-9.1: non-obvious choice of database locale

Date: Sun, 10 Feb 2013 19:35:48 +0100

Package: postgresql-9.1
Version: 9.1.7-1
Severity: wishlist

I am a fairly novice postgresql user, so I was just installing
postgresql-9.1 without any knowledge about database locale and how it
can go wrong. The installation procedure determined that LATIN1 would be
a perfect choice for my system, which lead to a number of problems later
on.

Given the number of issues that arise when using a non-UTF8 locale for
databases I suggest defaulting the locale to UTF8 and ignoring
environment variables used during installation and/or creating a
priority low debconf prompt for this.

Here is a list of problems which seem related.

#660209
#699453
https://www.blog.akendo.eu/debian-postgresql-8-4-cant-create-database-with-utf-8-encoding/
http://jacobian.org/writing/pg-encoding-ubuntu/

Feel free to disagree with me. In that case wontfix is your tag.

Helmut

Message #10 received at 700271@bugs.debian.org (full text, mbox, reply):

From: Frank Lanitz <frank@frank.uvena.de>

To: 700271@bugs.debian.org

Date: Sun, 10 Feb 2013 22:26:02 +0100

[Message part 1 (text/plain, inline)]

Hi,

I don't think this is a good idea.
Postgres should use default locale for system. If you have an
non-UTF-system nowadays, there might is good reason.

Cheers,
Frank

[signature.asc (application/pgp-signature, attachment)]

Message #17 received at 700271-done@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Helmut Grohne <helmut@subdivi.de>, 700271-done@bugs.debian.org

Subject: Re: [Pkg-postgresql-public] Bug#700271: postgresql-9.1: non-obvious choice of database locale

Date: Tue, 12 Feb 2013 16:15:46 +0100

[Message part 1 (text/plain, inline)]

tag 700271 wontfix
thanks

Hello Helmut,

Helmut Grohne [2013-02-10 19:35 +0100]:
> I am a fairly novice postgresql user, so I was just installing
> postgresql-9.1 without any knowledge about database locale and how it
> can go wrong. The installation procedure determined that LATIN1 would be
> a perfect choice for my system, which lead to a number of problems later
> on.

I seem to remember that this was because your system locale was in
fact a latin1 one, so the default was correct.

> Given the number of issues that arise when using a non-UTF8 locale for
> databases I suggest defaulting the locale to UTF8 and ignoring
> environment variables used during installation and/or creating a
> priority low debconf prompt for this.

I think defaulting to an encoding which doesn't match the system
locale is a rather bad idea, as that will cause even more problems
(like unexpected sorting or unreadable log messages).

You are right in the sense that non-UTF8 locales lead to a lot of
unexpected problems these days. I strongly recommend using an UTF-8
locale on your system.

So I respectfully "wontfix"/close this bug.

Thank you!

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 700271@bugs.debian.org (full text, mbox, reply):

From: Helmut Grohne <helmut@subdivi.de>

To: Martin Pitt <mpitt@debian.org>

Cc: 700271@bugs.debian.org

Subject: Re: [Pkg-postgresql-public] Bug#700271: postgresql-9.1: non-obvious choice of database locale

Date: Wed, 13 Feb 2013 08:17:13 +0100

On Tue, Feb 12, 2013 at 04:15:46PM +0100, Martin Pitt wrote:
> I seem to remember that this was because your system locale was in
> fact a latin1 one, so the default was correct.

TTBOMK there is no such thing as a "system locale". Can you briefly
point out what you mean and maybe how I could change it (or point me to
the corresponding documentation)?

My best guess at what you might mean would be LANG and LC_*, but this
can hardly be described as a system thingy. They are taken from the
environment of the connecting ssh client and the values defined on the
actual system in question are ignored. So clearly these are not system
settings, but session settings which a package installation should
obviously ignore. Still wondering what your "system locale" means.

Helmut

Message #27 received at 700271@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Helmut Grohne <helmut@subdivi.de>, 700271@bugs.debian.org

Subject: Re: [Pkg-postgresql-public] Bug#700271: postgresql-9.1: non-obvious choice of database locale

Date: Wed, 13 Feb 2013 08:29:53 +0100

Hello Helmut,

Helmut Grohne [2013-02-13  8:17 +0100]:
> TTBOMK there is no such thing as a "system locale". Can you briefly
> point out what you mean and maybe how I could change it (or point me to
> the corresponding documentation)?

I mean the default locale of a particular computer that is being used
if the user who logs in does not specify her own locale settings in
e. g. .bashrc or from ssh. This is usually set in /etc/default/locale
or, on older systems, in /etc/environment.

> My best guess at what you might mean would be LANG and LC_*, but this
> can hardly be described as a system thingy.

Right, these variables define the locale. System vs. User means where
they are set, in /etc/ as a default, or by the user as his/her
preference.

> They are taken from the environment of the connecting ssh client and
> the values defined on the actual system in question are ignored.

Ah, so that's what caused your problem? ssh set an invalid/bad locale
on the server where you set up PostgreSQL? sudo usually passes on
$LANG, su doesn't, so depending on how you install postgresql you
would have gotten the local or remote locale.

As a compromise, pg_createcluster (and thus apt-get install) could
show the locale of the generated cluster. Would that help?

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Message #32 received at 700271@bugs.debian.org (full text, mbox, reply):

From: Helmut Grohne <helmut@subdivi.de>

To: Martin Pitt <mpitt@debian.org>

Cc: 700271@bugs.debian.org

Subject: Re: [Pkg-postgresql-public] Bug#700271: postgresql-9.1: non-obvious choice of database locale

Date: Wed, 13 Feb 2013 08:49:13 +0100

On Wed, Feb 13, 2013 at 08:29:53AM +0100, Martin Pitt wrote:
> I mean the default locale of a particular computer that is being used
> if the user who logs in does not specify her own locale settings in
> e. g. .bashrc or from ssh. This is usually set in /etc/default/locale
> or, on older systems, in /etc/environment.

Both /etc/default/locale and /etc/environment are empty on the system in
question.  This likely represents the setting "C" that I usually make
during installation to avoid translation of messages.

> Right, these variables define the locale. System vs. User means where
> they are set, in /etc/ as a default, or by the user as his/her
> preference.

So the user setting appears to override the system setting here. That
appears like a bad idea to me, because the user setting really depends
on the remote system you are logging in from remotely.

In fact would postgresql have used my system setting the database
encoding should have been ASCII, right? Side question: Is there a way to
ask for UTF-8 without translation?

> Ah, so that's what caused your problem? ssh set an invalid/bad locale
> on the server where you set up PostgreSQL? sudo usually passes on
> $LANG, su doesn't, so depending on how you install postgresql you
> would have gotten the local or remote locale.

I sshed directly into the root account. In this case ssh will take the
LANG and LC_* variables from the client system, which in this case yes,
plausibly was responsible for the latin1 choice.

> As a compromise, pg_createcluster (and thus apt-get install) could
> show the locale of the generated cluster. Would that help?

Yes. That would likely have solved the issue in my case, because I would
have been wondering over latin1 in a database. I think that this
shouldn't target wheezy though.

The conclusion appears to be:

retitle 700271 mention database encoding used during installation
tags 700271 - wontfix

Thanks for your helpful reply.

Helmut

Message #47 received at 700271@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Helmut Grohne <helmut@subdivi.de>, 700271@bugs.debian.org

Subject: Re: [Pkg-postgresql-public] Bug#700271: postgresql-9.1: non-obvious choice of database locale

Date: Wed, 13 Feb 2013 11:14:01 +0100

Hello Helmut,

Helmut Grohne [2013-02-13  8:49 +0100]:
> Both /etc/default/locale and /etc/environment are empty on the system in
> question.  This likely represents the setting "C" that I usually make
> during installation to avoid translation of messages.

Note that this also means that you cannot use any non-ASCII characters
anywhere, including file names, shell commands, etc. and get a rather
odd-looking date, printer papersize, and whatnot. locale is a lot more
than just translations.

> 
> In fact would postgresql have used my system setting the database
> encoding should have been ASCII, right?

Correct.

> Side question: Is there a way to ask for UTF-8 without translation?

Sure, set LANG=de_DE.UTF-8 and LC_MESSAGES=C . That will still use
UTF-8 character encoding/sorting (LC_CTYPE, LC_COLLATE), and region
settings (LC_PAPER, LC_TIME, LC_PAPER, etc.), but display the plain C
(untranslated) strings.

> I sshed directly into the root account. In this case ssh will take the
> LANG and LC_* variables from the client system, which in this case yes,
> plausibly was responsible for the latin1 choice.

Indeed.

> > As a compromise, pg_createcluster (and thus apt-get install) could
> > show the locale of the generated cluster. Would that help?
> 
> Yes. That would likely have solved the issue in my case, because I would
> have been wondering over latin1 in a database. I think that this
> shouldn't target wheezy though.
> 
> The conclusion appears to be:
> 
> retitle 700271 mention database encoding used during installation
> tags 700271 - wontfix

Agreed, thanks!

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Message #52 received at 700271@bugs.debian.org (full text, mbox, reply):

From: Helmut Grohne <helmut@subdivi.de>

To: Martin Pitt <mpitt@debian.org>

Cc: 700271@bugs.debian.org

Subject: Re: [Pkg-postgresql-public] Bug#700271: postgresql-9.1: non-obvious choice of database locale

Date: Thu, 14 Feb 2013 10:53:57 +0100

Control: reopen -1
Control: retitle -1 mention database encoding used during installation
Control: tags -1 - wontfix

On Wed, Feb 13, 2013 at 11:14:01AM +0100, Martin Pitt wrote:
> Sure, set LANG=de_DE.UTF-8 and LC_MESSAGES=C . That will still use
> UTF-8 character encoding/sorting (LC_CTYPE, LC_COLLATE), and region
> settings (LC_PAPER, LC_TIME, LC_PAPER, etc.), but display the plain C
> (untranslated) strings.

Thanks. I tried this, but it appears to have unintended side effects.
For instance I really expect LC_COLLATE=C when using sort or sed. I am
similarly accustomed to LC_TIME=C by now. Scripts not expecting non-C
locales used to be frequent issues in Debian, but still are for my
personal scripts.

I also noticed that the pg_createcluster(8) is quite precise on the
locale settings used. This is great. Do you think that having the locale
preseedable[1] would be a worthwhile feature? I could not find out
whether the locale settings are used when installing packages via "d-i
pkgsel/include string".

> Agreed, thanks!

Metadata updated.

Helmut

[1] http://wiki.debian.org/DebianInstaller/Preseed

Message #59 received at 700271-close@bugs.debian.org (full text, mbox, reply):

From: Christoph Berg <myon@debian.org>

To: 700271-close@bugs.debian.org

Subject: Bug#700271: fixed in postgresql-common 141

Date: Wed, 10 Apr 2013 15:32:56 +0000

Source: postgresql-common
Source-Version: 141

We believe that the bug you reported is fixed in the latest version of
postgresql-common, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 700271@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Berg <myon@debian.org> (supplier of updated postgresql-common package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 10 Apr 2013 16:25:06 +0200
Source: postgresql-common
Binary: postgresql-common postgresql-client-common postgresql-server-dev-all postgresql postgresql-client postgresql-doc postgresql-contrib
Architecture: source all
Version: 141
Distribution: experimental
Urgency: low
Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Description: 
 postgresql - object-relational SQL database (supported version)
 postgresql-client - front-end programs for PostgreSQL (supported version)
 postgresql-client-common - manager for multiple PostgreSQL client versions
 postgresql-common - PostgreSQL database-cluster manager
 postgresql-contrib - additional facilities for PostgreSQL (supported version)
 postgresql-doc - documentation for the PostgreSQL database management system
 postgresql-server-dev-all - extension build tool for multiple PostgreSQL versions
Closes: 682938 689996 700271 701602
Changes: 
 postgresql-common (141) experimental; urgency=low
 .
   [ Christoph Berg ]
   * debian/maintscripts-functions: Fix configure_client_version to call
     _link_manpages correctly, spotted by Kris Shannon. (Closes: #701602)
   * debian/postgresql-common.sysctl: Note that the file is Linux-specifc and
     do some rewording of the comments.
   * debian/supported-versions:
     + Deprecate 8.3 for pgdg builds.
     + Handle missing os-release and lsb_release gracefully, just print a
       warning. (Affects squeeze systems, Introduced by the fix for #697182).
   * pg_buildext: Deprecate <srcdir> parameter. The docs do not mention it
     anymore, but the script will still accept it.
   * pg_createcluster, pg_upgradecluster: For 9.2 and higher, use the new
     ssl_ca_file option instead of creating a root.crt symlink in the data
     directory. (Related to the fix for #680162 below.)
   * pg_createcluster: If /etc/postgresql-common/root.crl is present, symlink
     it (<= 9.1), or set ssl_crl_file (>= 9.2).
   * pg_ctlcluster: Create (first) unix_socket_directory if missing.
   * pg_ctlcluster: Document start.conf by pointing at pg_createcluster(8).
   * pg_lsclusters: Make output column widths dynamically adjust to contents;
     shorten "Version" in header to "Ver".
   * pg_upgradecluster: Get cluster encoding before shutting down the cluster
     so we don't need to restart it in pg_upgrade mode; temporarily start the
     cluster if needed.
   * postgresql-client-common: For apt.postgresql.org builds (with "pgdg" in
     the version number), depend on pgdg-keyring.
   * Add a "apt.postgresql.org.sh" script to add that archive to sources.list.
 .
   [ Martin Pitt ]
   * debian/backport-ppa: Stop building raring packages. The PPA is declared
     deprecated now, moving to apt.postgresql.org.
   * pg_createcluster: Drop "Moving configuration file.." message as it's not
     all that interesting and we are going to add more status output.
   * pg_createcluster: Print configuration and data directory on separate
     lines, and also show the current locale that the cluster will use.
     (Closes: #700271)
   * pg_updatedicts: Cleanup tsearch data files which do not have a
     corresponding hunspell or myspell dictionary installed any more.
     (Closes: #689996)
   * Adjust upgrade tests according to the changed pg_lscluster formatting.
 .
   [ Peter Eisentraut ]
   * Add support for pg_upgrade: (Closes: #682938)
     - pg_upgradecluster: Add options to select pg_upgrade instead of
       dump/restore, and call pg_upgrade when selected.
     - t/040_upgrade.t: Test all upgrade methods.
Checksums-Sha1: 
 c3ff5837ac4b97ca919f569a844303c50b52db55 2151 postgresql-common_141.dsc
 130fb5d0a65308ebbfee8f544db87889a08b3856 157076 postgresql-common_141.tar.gz
 25d5246d298d71c61546d253887785d581e06a53 50076 postgresql-server-dev-all_141_all.deb
 f11ef1a6bbad71e77b6fd4b059ca8d35dac46535 45476 postgresql_9.1+141_all.deb
 ae53ba4ea3b55f5db97b57f2fffcc957efff572c 45502 postgresql-client_9.1+141_all.deb
 8dbc41f10cab67e883037b9adc52aebfb5287f67 45486 postgresql-doc_9.1+141_all.deb
 cfcdfcb415b8151bc0bc069786f46775464dfb7a 45506 postgresql-contrib_9.1+141_all.deb
 48a126055815c5d6fa74557084478eeef86c87d4 150770 postgresql-common_141_all.deb
 ce78043e8ceb6c723ce16ca90f892c9cd35fa284 66226 postgresql-client-common_141_all.deb
Checksums-Sha256: 
 0788c47ef0fe0a732cd2862b2369838eef71e1d32e7258327aace312baf42a42 2151 postgresql-common_141.dsc
 43a2c7bb94b726e305052bf6b4504efce5a7b6eef68ef87d70b82caad7bff62f 157076 postgresql-common_141.tar.gz
 08e770d9d2d82dd504474781187cfc9e01a727b959131ba057227fafe19f690f 50076 postgresql-server-dev-all_141_all.deb
 ff0950870c3b94185052c11435d85dde66405d025f5fde15d145bb35c6a48aeb 45476 postgresql_9.1+141_all.deb
 1e43bee751057c20f3597b42a380d723aae2b0442420d0d9dd12779ee8fa5069 45502 postgresql-client_9.1+141_all.deb
 92d2c74bd1f3cd9e7548ffd262b57e2ce508b219f46d72752512f609f2872594 45486 postgresql-doc_9.1+141_all.deb
 5074af1d28708c512092fff8d66afda716be539c4e9a8c518892ad43be061436 45506 postgresql-contrib_9.1+141_all.deb
 47aa7cae15c17a2bcb7a8df2bb9c1e1debc36d5dcb2ee1838aee0bbe031c3fb9 150770 postgresql-common_141_all.deb
 d70033712457ddd80052e2c966bb6ce4c2a52f1a4286a60908fa913a811e731e 66226 postgresql-client-common_141_all.deb
Files: 
 661d6b2e9405edc1ef1d0aed256800ff 2151 database optional postgresql-common_141.dsc
 5bf09bdf7aadb5aea941582ce5a93f8a 157076 database optional postgresql-common_141.tar.gz
 a3ebff82a762b845b45b618092ab2f34 50076 database optional postgresql-server-dev-all_141_all.deb
 3d2b35302f5d28b3ddf8c904fa266951 45476 database optional postgresql_9.1+141_all.deb
 c204e81eff3dad343b4edf2f7314919d 45502 database optional postgresql-client_9.1+141_all.deb
 ebc1b71c9b8884575d42f0338f66e4b7 45486 doc optional postgresql-doc_9.1+141_all.deb
 0357e3bc0f0e0457bcdca4cdd82f55eb 45506 database optional postgresql-contrib_9.1+141_all.deb
 163c173a634468ec31146d60ffb4bb02 150770 database optional postgresql-common_141_all.deb
 cd42bd148a6d1f17043e3ab2c9851ef1 66226 database optional postgresql-client-common_141_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRZYQoAAoJEExaa6sS0qeugNMP/1kZJQnwMDFlaGdEyStZbTur
uIrTDSN+za2ijd5szibcAuUBgp61osgxrumbwvNcE0LEUENn9eJjubybwkQCCRqu
U5MH8pLENSFM8ThMbrfVW7AnVyJ7LhLyCW8YXtBS8zFAAcYJ5uSVcDYDJmCUehMi
IXMn+q4R5E7iTSGZUaxOzpkSm37+F0+6zo5Lac/9zVE5DKyGWhag2k44XJptqVdg
A2FOps/Mrz3FsLh2Wi3lHUJXW2VJsXp3Y2JHi0Ru8sG50aTvX8vbROKqn+N8yOun
de6AK6U9f1Bhh6iemr7Qykg57U9gVzj4l9BEZnar7eObnD9HWwhfztT6se0VdN4Z
5WFLMF04ChuCnsaNFRMyY8JV28LWC74QYMBcUI/SLcJOpa89EnP4Ih4aIDz9gHC8
t/uYkmHpEoRGzGMyflYrhlXsaSTqkv6MTJhniO8EoiDw1fFyWWhyIPj05Lpe9nHM
fjA7/nOMDLJEGylvCSY/3QlbJ63g6zxTJRG2PovcQ2McI4fw+T7aqsU6IhozbyTF
fgIVyhNX9Ws2Oc9slkqoQNNYIwgEHp4+OfP4TSxrsoS0kGWAG8ClV7bYzynAl6GM
PCXLq2nW23F0B8iyo5ueTz2WinLqieEeEsGNthtLKZ9LPAzTeEpwU69th8fQJou+
AqMisMkax8G/ZXoOj+Ft
=mNCJ
-----END PGP SIGNATURE-----

Message #64 received at 700271-close@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: 700271-close@bugs.debian.org

Subject: Bug#700271: fixed in postgresql-common 142

Date: Tue, 07 May 2013 10:19:35 +0000

Source: postgresql-common
Source-Version: 142

We believe that the bug you reported is fixed in the latest version of
postgresql-common, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 700271@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@debian.org> (supplier of updated postgresql-common package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 07 May 2013 11:11:58 +0200
Source: postgresql-common
Binary: postgresql-common postgresql-client-common postgresql-server-dev-all postgresql postgresql-client postgresql-doc postgresql-contrib
Architecture: source all
Version: 142
Distribution: unstable
Urgency: low
Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Martin Pitt <mpitt@debian.org>
Description: 
 postgresql - object-relational SQL database (supported version)
 postgresql-client - front-end programs for PostgreSQL (supported version)
 postgresql-client-common - manager for multiple PostgreSQL client versions
 postgresql-common - PostgreSQL database-cluster manager
 postgresql-contrib - additional facilities for PostgreSQL (supported version)
 postgresql-doc - documentation for the PostgreSQL database management system
 postgresql-server-dev-all - extension build tool for multiple PostgreSQL versions
Closes: 637017 639108 646700 650680 656363 671915 677604 680162 680571 681344 682938 685043 688105 689994 689996 693958 697182 697239 697291 697377 698958 699911 700271 701602 705219
Changes: 
 postgresql-common (142) unstable; urgency=low
 .
   [ Christoph Berg ]
   * Make all scripts honor PGSYSCONFDIR (defaulting to
     /etc/postgresql-common).
   * The default behavior of pg_createcluster can be configured in
     /etc/postgresql-common/createcluster.conf. This also allows to disable the
     creation of "main" clusters when postgresql server packages are installed,
     and to set parameters in the new postgresql.conf.
   * pg_createcluster: Move setting of log_line_prefix to createcluster.conf.
   * debian/postgresql-common.postgresql.init: Do not die of one cluster fails
     to start. (Closes: #699911)
   * pg_checksystem: Suppress error message for unavailable filesystems.
     (Closes: #705219)
   * pg_upgradecluster: Use a distinct name (pg_hba.conf.pg_upgradecluster) for
     the pg_hba.conf backup, and handle the case where this file already exists
     gracefully.
   * pg_upgradecluster: On upgrades to 9.3, rename unix_socket_directory to
     unix_socket_directories.
   * pg_upgradecluster, t/043_upgrade_ssl_cert.t: Copy server.crt and friends
     in the data directory on upgrade. (Closes: #698958)
   * pg_ctlcluster: Set LANG so non-ascii chars in the server log are not
     replaced by '?'. Thanks to Adrian Vondendriesch for help debugging this.
     (Closes: #671915)
 .
   [ Martin Pitt ]
   * debian/supported-versions: Add 9.3 for testing/unstable.
   * debian/supported-versions: Add Ubuntu 13.10.
   * Bump Standards-Versio to 3.9.4 (no changes necessary).
   * pg_upgradecluster: For upgrades to 9.3, migrate "replication_timeout" to
     "wal_sender_timeout".
   * t/060_obsolete_confparams.t: Add full 9.2 configuration, to test 9.2 → 9.3
     upgrades.
 .
 postgresql-common (141) experimental; urgency=low
 .
   [ Christoph Berg ]
   * debian/maintscripts-functions: Fix configure_client_version to call
     _link_manpages correctly, spotted by Kris Shannon. (Closes: #701602)
   * debian/postgresql-common.sysctl: Note that the file is Linux-specifc and
     do some rewording of the comments.
   * debian/supported-versions:
     + Deprecate 8.3 for pgdg builds.
     + Handle missing os-release and lsb_release gracefully, just print a
       warning. (Affects squeeze systems, Introduced by the fix for #697182).
   * pg_buildext: Deprecate <srcdir> parameter. The docs do not mention it
     anymore, but the script will still accept it.
   * pg_createcluster, pg_upgradecluster: For 9.2 and higher, use the new
     ssl_ca_file option instead of creating a root.crt symlink in the data
     directory. (Related to the fix for #680162 below.)
   * pg_createcluster: If /etc/postgresql-common/root.crl is present, symlink
     it (<= 9.1), or set ssl_crl_file (>= 9.2).
   * pg_ctlcluster: Create (first) unix_socket_directory if missing.
   * pg_ctlcluster: Document start.conf by pointing at pg_createcluster(8).
   * pg_lsclusters: Make output column widths dynamically adjust to contents;
     shorten "Version" in header to "Ver".
   * pg_upgradecluster: Get cluster encoding before shutting down the cluster
     so we don't need to restart it in pg_upgrade mode; temporarily start the
     cluster if needed.
   * postgresql-client-common: For apt.postgresql.org builds (with "pgdg" in
     the version number), depend on pgdg-keyring.
   * Add a "apt.postgresql.org.sh" script to add that archive to sources.list.
 .
   [ Martin Pitt ]
   * debian/backport-ppa: Stop building raring packages. The PPA is declared
     deprecated now, moving to apt.postgresql.org.
   * pg_createcluster: Drop "Moving configuration file.." message as it's not
     all that interesting and we are going to add more status output.
   * pg_createcluster: Print configuration and data directory on separate
     lines, and also show the current locale that the cluster will use.
     (Closes: #700271)
   * pg_updatedicts: Cleanup tsearch data files which do not have a
     corresponding hunspell or myspell dictionary installed any more.
     (Closes: #689996)
   * Adjust upgrade tests according to the changed pg_lscluster formatting.
 .
   [ Peter Eisentraut ]
   * Add support for pg_upgrade: (Closes: #682938)
     - pg_upgradecluster: Add options to select pg_upgrade instead of
       dump/restore, and call pg_upgrade when selected.
     - t/040_upgrade.t: Test all upgrade methods.
 .
 postgresql-common (140) experimental; urgency=low
 .
   [ Martin Pitt ]
   * t/001_packages.t: Also check that -contrib is installed.
   * debian/backport-ppa: Backport -common for Ubuntu 12.10.
   * PgCommon.pm: Recognize "include_if_exists" directive. (LP: #1098986)
   * pg_ctlcluster: Recreate a missing /var/log/postgresql/ if needed.
     (LP: #1009989)
   * debian/postgresql-client-common.links: Wrap pgbench with pg_wrapper.
     (LP: #1068194)
 .
   [ Christoph Berg ]
   * testsuite: The default list of umasks to test (022 077) can be overridden
     by setting the environment variable PG_UMASKS.
   * t/003_package_checks.t: Ensure psql is linked against libedit.
   * t/005_PgCommon.t: Increase sleep time after netcat launch to 200ms.
   * t/020_create_sql_remove.t: Test process title update.
   * pg_createcluster: Allow passing of initdb arguments on the command line.
     If --auth parameters are passed, skip updating the generated pg_hba.conf
     file.
   * pg_virtualenv: Allow passing initdb arguments to pg_createcluster.
   * pg_upgradecluster: Print a helpful message when invoked on the target
     version. Problem seen on #postgresql.
   * t/030_errors.t: Adjust testsuite for this.
   * debian/supported-versions: Handle unset variables from /etc/os-release
     gracefully. Spotted by x4rlos on #postgresql.
   * pg_buildext: Set USE_PGXS=1, and srcdir (needed by plr).
 .
 postgresql-common (139) experimental; urgency=low
 .
   [ Christoph Berg ]
   * pg_virtualenv: New program to create throw-away clusters for running
     regression tests.
   * testsuite: unshare needs "--" or else it eats our options.
   * testsuite: Require netcat-openbsd to be installed.
   * testsuite: Move locale generation here from debian/tests/system, also
     generate en_US.utf8 locale; unset LC_ALL.
   * Drop debian/tests, moved to the postgresql-* server packages.
   * testsute 005_PgCommon: Do the ipv4 tests before the ipv6 ones; skip
     the ipv6 for perl <= 5.10 (i.e. on squeeze and lucid).
   * PgCommon.pm, pg_ctlcluster, pg_createcluster, t/030_errors.t: 9.3 renames
     unix_socket_directory to unix_socket_directories.
   * pg_wrapper: Document that PGHOST overrides PGCLUSTER. (Closes: #697291)
   * pg_wrapper: Skip cluster selection if --host is given on the command line.
     (Closes: #637017) While we are at it, improve --port parsing, too.
   * t/010_defaultport_cluster.t: Add test cases for the above pg_wrapper
     changes.
   * t/040_upgrade.t: dup2 psql stderr to suppress warning 'could not change
     directory to "/tmp/pgtest'.
   * postgresql-client-common: Add Depends: netbase for getprotobyname() in
     PgCommon.pm. (Closes: #697377)
 .
   [ Martin Pitt ]
   * debian/supported-versions: Read /etc/os-release if present, and fall back
     to lsb-release. Exit with a proper error message if neither is present.
     This gets rid of the (currently undeclared) strict dependency on
     lsb-release. (Closes: #697182)
   * debian/README.Debian: Update versions to 8.4/9.1, as current for Squeeze
     and Wheezy. (Closes: #697239)
 .
 postgresql-common (138) experimental; urgency=low
 .
   [ Christoph Berg ]
   * testsuite: start localhost interface which is down after unshare -n.
 .
   [ Martin Pitt ]
   * testsuite: Stop currently running clusters, just as the script has done
     until 136.
   * testsuite: Use a more elegant way of re-execing ourselves through unshare.
 .
 postgresql-common (137) experimental; urgency=low
 .
   [ Martin Pitt ]
   * debian/backport-ppa: Disable xz compression for lucid.
   * debian/backport-ppa: Disable libraries for -9.1/natty as well, built by
     9.2 now.
   * debian/backport-ppa: Ensure that backport PPA versions are always smaller
     than the versions in -updates.
   * pg_wrapper: Always use the latest available client version of "psql"
     instead of the target cluster's. psql is backwards compatible to all major
     versions that we support in any release. Update tests to use "createdb"
     instead of "psql" for --version tests, and add a new test for the psql
     special case to t/020_create_sql_remove.t. (Closes: #639108)
   * debian/postgresql-common.triggers: Also watch for changes in
     /usr/share/hunspell/; pg_updatedicts handles these as well.
     (Closes: #689994)
   * debian/tests/control: Add netcat-openbsd test dependency for the
     next_free_port() tests added below.
   * debian/backport-ppa: Drop natty (EOL), add raring for 9.2.
   * debian/supported-versions: Add Ubuntu 13.04.
   * testsuite: Run with overlaid tmpfses on the postgresql /etc/ and /var
     directories in an unshared namespace. This is more robust against
     protecting existing clusters, always cleans up after itself properly, and
     also speeds up testing.
   * t/031_errors_disk_full.t: Drop check for existence of unshare, as
     ./testsuite now unconditionally requires it.
   * debian/postgresql-common.postinst: Only chown /var/lib/postgresql if it
     does not already have the correct ownership. This avoids failures when the
     directory is NFS mounted. Thanks Hugh Davenport! (Closes: #693958)
 .
   [ Christoph Berg ]
   * testsuite: Move 'disk full' tests from 030_errors to new file
     031_errors_disk_full.
   * testsuite: Note that Test::More 0.87 is required for done_testing() in
     170_extensions.
   * testsuite 005_PgCommon: Add next_free_port tests (using /bin/nc).
   * supported-versions: Make output configurable via $PG_SUPPORTED_VERSIONS,
     ~/.pg_supported_versions, and /etc/postgresql-common/supported_versions.
     (Closes: #646700)
   * supported-versions: Add debian-backports and pgdg sections.
     (Closes: #650680)
   * For bpo and pgdg builds (determined by the version number), create
     /etc/postgresql-common/supported_versions with appropriate content.
   * Replace version string comparisions in perl scripts to use numerical
     operators, so things will continue to work when PostgreSQL 10.0 is
     released.
   * debian/rules: Use sort -n for sorting supported-versions output.
   * debian/rules: Use apt-cache policy instead of apt-cache show to determine
     the "candidate" logrotate version.
   * testsuite 020_create_sql_remove: Fix plperl test to work with 8.2.
   * testsuite 085_pg_ctl.conf: Skip for 8.2.
 .
 postgresql-common (136) experimental; urgency=low
 .
   [ Martin Pitt ]
   * debian/backport-ppa: Do first upload with orig tarball, subsequent ones
     without.
   * debian/backport-ppa: Do not run lintian.
   * debian/backport-ppa: When building postgresql-9.1 for lucid, drop the
     library packages as they collide with the ones built from postgresql-9.2.
   * debian/backport-ppa: Build 9.2 for Quantal and Natty.
   * debian/supported-versions: Add Ubuntu 12.10.
   * t/030_errors.t: For the "fails on insufficient disk space test", move from
     setting up a loop device to a tmpfs in unshare -m. This is more robust for
     cleaning up after itself, and faster as well.
   * pg_ctlcluster: Fix log output to stderr if the log file started out being
     empty. Add test case to t/030_errors.t.
   * debian/maintscripts-functions: Only try to remove the tsearch_data
     directory  if it already exists. Thanks Peter Palfrader. (Closes: #688105)
 .
   [ Christoph Berg ]
   * pg_buildext: Fix supported-versions not to die when the last version is
     not supported.
   * testsuite: Add getopt handling, and make the list of umasks to loop
     through configurable (-u).
   * t/001_packages.t: Print list of installed versions for information.
   * As debian/supported-versions is also used at build-time, add a
     build-dependency on lsb-release for lsb_release to be available. Also,
     print supported versions from debian/rules for easier debugging.
 .
 postgresql-common (135) experimental; urgency=low
 .
   [ Martin Pitt ]
   * pg_createcluster: For 9.2 and higher, use the new ssl_{cert,key}_file
     options instead of creating symlinks in the data directory.
     (Closes: #680162)
   * pg_upgradecluster: Set above options to the old cluster's SSL cert/key
     symlink destinations, if they exist.
   * debian/maintscripts-functions: Configure alternatives for manpages in
     -contrib. This will only take effect after (re)installing
     postgresql-contrib-9.2. (Closes: #680571)
   * debian/postgresql-common.postgresql.init: Fix "status" output to be more
     useful and legible, and exit with code 3 if any cluster is down.
     (Closes: #656363)
   * debian/postgresql-common.postgresql.init: Show a warning message if no
     clusters exist. (Closes: #677604)
   * t/041_upgrade_custompaths.t: Run test with a cluster that is down, to
     verify that pg_upgradecluster works for non-running clusters, too.
   * pg_upgradecluster: Move encoding detection after restarting the cluster
     with restricted connections, and drop the check that the cluster is
     running. With this, pg_upgradecluster also works for clusters which are
     not running. (Closes: #681344)
 .
   [ Peter Eisentraut ]
   * pg_createcluster: For PostgreSQL >= 9.2, use initdb options to set the
     default authentication methods, instead of modifying the configuration
     file directly. (Closes: #685043)
Checksums-Sha1: 
 342d417323bb780eb6ac1de862f45de37f360e06 2151 postgresql-common_142.dsc
 0bb0ab92516b8494d6f494d61773e455bf7ec968 160503 postgresql-common_142.tar.gz
 38eeca24a73ec85db7af7543d8ced7f15738df20 50490 postgresql-server-dev-all_142_all.deb
 860cd1b444a70fa27483a0cd5ff6eaa4947496bc 45838 postgresql_9.3+142_all.deb
 e17875031adfb01cbb916d6235b96733366c3ffe 45852 postgresql-client_9.3+142_all.deb
 7fddd6d8d45d784cb3edf02ba5f1b5775aa56876 45846 postgresql-doc_9.3+142_all.deb
 fa12fac713e2f6e8d176e6930cd021fe071bdcc6 45860 postgresql-contrib_9.3+142_all.deb
 6fad4530df728b18bb2a7e5385dcd488770158fc 153600 postgresql-common_142_all.deb
 33289e9aabc98869047448d046b1a0ca044679dc 67232 postgresql-client-common_142_all.deb
Checksums-Sha256: 
 d4821b69a4d766d0ddd739322b141b4c9fe7690ed38f402e6e77b975f1056c23 2151 postgresql-common_142.dsc
 1f018b536b596e7f35c6b8c4dc908eded7f04b1c13763ecbcb34c6bd24f69bc7 160503 postgresql-common_142.tar.gz
 4be5b47a558e0223d92166983d69a7e03e672b48b20f9a70d4b237b26156d8ed 50490 postgresql-server-dev-all_142_all.deb
 dbcb7f04d78a88463b04880e028403e09c6acdcd0d6c0244ebef36dddc37104e 45838 postgresql_9.3+142_all.deb
 4dabd33460879cf280740a98a5f5c67702e87f036d3357afeaa14a5bd01c83bc 45852 postgresql-client_9.3+142_all.deb
 ffa831613e44a31d375c2f4e57cdb87f2737abccf44fb1830e568da576a7450c 45846 postgresql-doc_9.3+142_all.deb
 259a51001944600b9c27cd67ea9f261634835d7d948d952bcfa3e60da08f9b6d 45860 postgresql-contrib_9.3+142_all.deb
 eb45ce6438e776fd790af07f41c6f32f672eea808552da2884903e1ccb533b80 153600 postgresql-common_142_all.deb
 8f21d672f6b57bee994c7d4cb9b55dcc04140213c9fea25345ede156552d9493 67232 postgresql-client-common_142_all.deb
Files: 
 e3dc96d96853c8f620960ad1cecb79d5 2151 database optional postgresql-common_142.dsc
 1f031473458484bc3570ccb044e969a5 160503 database optional postgresql-common_142.tar.gz
 7daec11778e8e92ed9741dd70ce349f1 50490 database optional postgresql-server-dev-all_142_all.deb
 10419d7dc90544badf00adf33a7588d6 45838 database optional postgresql_9.3+142_all.deb
 c525b365dff6367bf4be3f1c682c7cb7 45852 database optional postgresql-client_9.3+142_all.deb
 5ddc6f43935ad08b0ed322be881147f0 45846 doc optional postgresql-doc_9.3+142_all.deb
 4534770300ea0851842bbfa3f05d8ddd 45860 database optional postgresql-contrib_9.3+142_all.deb
 6452ba3591032bed2ede496ef4b2a971 153600 database optional postgresql-common_142_all.deb
 f1b82f89189bc7abfa69a6a4476a66a1 67232 database optional postgresql-client-common_142_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRiNAhAAoJEPmIJawmtHufkGYP/30jGXibpf5BGCY6b24Us6tN
fR93yb2s48Cw4CLozL4CNjh+ZgID0upazWHnUSfrVMFaiGfpc2WI+2HCR1As/d0N
zVmKK6KMRTmG7FvjcClbuZkGC7pMnTq+b+v/YZrNbiuPbTZKfYJCGDUjDZIe9xWL
3X9hA6R700oR8JhP2bxt7x1MSrcHD1sIe8E88rH5BlpI8E7CqrmexjaxQxj4MM3j
ShDRbkts896pFxvl8x9uwReUjmyLITbfd6V/AmrW1ByOTjBXTAvNfLqa4wrpOmph
NWf54a73sQGAa+63JKEDLAYZGA0UQ+TmmYbRxk94CKhjNgpgpHcz5BhLpQCsr/08
pIZSANQRRaKmjFePjHLohsTbua2n5Ze1r/qOZ9vpNFAKhPdOPFb1U6ouTssjQzVS
CrCsEVG7CZCVGcylgQfdkU/DBzpQ7VgElYxvmdhV18QMosfhxnAQIQPQMp7QnRds
BAYdaeeGPHtY7BOjxGj5rttkJpEq8yeOFq986ofbgrLwuhl/nhDskH/1H5T6zEv1
vVmMgLNgV7HgT8+0MPgO1EKWd2dapuxuOhoe57SxdMzTd+mdYVmpkY3tOlzFuwah
GJVsq6PxgGDe46YF8+D9wIOHVFQFPDw7SElBDuF4KdtNHC09u4wLtLSkxMghu75F
pGpDXylAltuxdefPlCIN
=Y/7R
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.