Your message dated Tue, 07 Jun 2005 06:32:49 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#241337: fixed in postgresql-common 15
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 31 Mar 2004 22:22:13 +0000
>From [EMAIL PROTECTED] Wed Mar 31 14:22:13 2004
Return-path: <[EMAIL PROTECTED]>
Received: from io.link-m.de [195.30.85.225] (daemon)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B8o68-0002uG-00; Wed, 31 Mar 2004 14:22:13 -0800
Received: from localhost (localhost [127.0.0.1])
(uid 1004)
by io.link-m.de with local; Thu, 01 Apr 2004 00:22:11 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Julian Mehnle <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: postgresql: Multiple "Could not save old binaries" messages when
updating
from 7.3.4-9 to 7.4.2-1
X-Mailer: reportbug 2.54
Date: Thu, 01 Apr 2004 00:22:11 +0200
Message-ID: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,DATING,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: postgresql
Version: 7.4.2-1
Severity: normal
Today, I updated from 7.3.4-9 to 7.4.2-1 on two different Debian/Testing
machines. On both machines, during the update, I got multiple instances
of the following message:
Could not save old binaries
As a result, an automatic upgrade (using `postgresql-dump`, I guess) of
my databases was not attempted, which was inconvenient. As I updated
quite a few other services at the same time that depend on one of my
PostgreSQL databases, the overall upgrade wasn't a very nice experience,
as the postmaster wasn't running when the other services tried to
restart. (Yeah, I know I shouldn't rely on the automatic database
upgrade feature, but still...)
I think the upgrade scripts should have been able to "save the old
binaries". It worked fine twice before on these machines (7.1 -> 7.2 ->
7.3). Only today, with 7.4, it failed systematically.
Yes, I read /usr/share/doc/postgresql/README.Debian.migration.gz after
the upgrade failed on the first machine, and I removed
/var/lib/postgres/dumpall/7.3/ (which existed on both machines), as
suggested in the "Wrong program version saved" section, before trying the
update on the second machine. But it still failed in exactly the same
way.
This is an excerpt of the relevant parts of how the update went:
----------8<----------snip----------8<----------
[...]
apt-listchanges: Mailing changelogs to root
Preconfiguring packages ...
[...]
Preparing to replace libpq3 7.3.4-9 (using .../libpq3_7.4.2-1_i386.deb)
[...]
Could not save old binaries
Unpacking replacement libpq3 ...
Preparing to replace postgresql 7.3.4-9 (using
.../postgresql_7.4.2-1_i386.deb) ...
Stopping PostgreSQL database: postmaster
waiting for postmaster to shut down......done
postmaster successfully shut down
.
Could not save old binaries
Unpacking replacement postgresql ...
Preparing to replace postgresql-client 7.3.4-9 (using
.../postgresql-client_7.4.2-1_i386.deb) ...
Could not save old binaries
Unpacking replacement postgresql-client ...
[...]
Setting up postgresql-client (7.4.2-1) ...
Setting up postgresql (7.4.2-1) ...
Installing new version of config file /etc/postgresql/postgresql.conf
[...]
Installing new version of config file /etc/postgresql/postmaster.conf
[...]
Installing new version of config file /etc/postgresql/pg_hba.conf ...
Installing new version of config file /etc/cron.d/postgresql ...
Installing new version of config file /etc/init.d/postgresql ...
[...]
---------->8----------snap---------->8----------
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (600, 'testing'), (90, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 2.4.25-1-k6
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages postgresql depends on:
ii adduser 3.51 Add and remove users and groups
ii debconf [debconf 1.4.16 Debian configuration management sy
ii debianutils 2.7.2 Miscellaneous utilities specific t
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libcomerr2 1.35-3 The Common Error Description libra
ii libkrb53 1.3.2-2 MIT Kerberos runtime libraries
ii libpam0g 0.76-15 Pluggable Authentication Modules l
ii libperl5.8 5.8.3-2 Shared Perl library.
ii libpq3 7.4.2-1 Shared library libpq.so.3 for Post
ii libreadline4 4.3-10 GNU readline and history libraries
ii libssl0.9.7 0.9.7d-1 SSL shared libraries
ii mailx 1:8.1.2-0.20031014cvs-1 A simple mail user agent
ii postgresql-clien 7.4.2-1 Front-end programs for PostgreSQL
ii procps 1:3.2.0-1 The /proc file system utilities
ii python2.3 2.3.3-6 An interactive high-level object-o
ii zlib1g 1:1.2.1-5 compression library - runtime
-- debconf information:
* postgresql/initdb/location: /var/lib/postgres/data
* postgresql/upgrade/preserve_location: /var/lib/postgres/preserve
* postgresql/settings/day_month_order: European
postgresql/convert-postmaster.init: true
* postgresql/upgrade/policy: true
* postgresql/settings/locale: C
postgresql/peer-to-ident: true
postgresql/enable_lang: true
postgresql/missing_conf: true
postgresql/contains_POSTGRESHOME: true
* postgresql/purge_data_too: false
postgresql/very_old_version_warning: true
* postgresql/upgrade/dump_location: /var/lib/postgres
* postgresql/settings/encoding: UNICODE
postgresql/convert-pg_hba.conf: true
* postgresql/settings/date_style: ISO
---------------------------------------
Received: (at 241337-close) by bugs.debian.org; 7 Jun 2005 10:38:32 +0000
>From [EMAIL PROTECTED] Tue Jun 07 03:38:32 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DfbTb-0005GM-00; Tue, 07 Jun 2005 03:38:32 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DfbO5-0004II-00; Tue, 07 Jun 2005 06:32:49 -0400
From: Martin Pitt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#241337: fixed in postgresql-common 15
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 07 Jun 2005 06:32:49 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 7
Source: postgresql-common
Source-Version: 15
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:
postgresql-common_15.dsc
to pool/main/p/postgresql-common/postgresql-common_15.dsc
postgresql-common_15.tar.gz
to pool/main/p/postgresql-common/postgresql-common_15.tar.gz
postgresql-common_15_all.deb
to pool/main/p/postgresql-common/postgresql-common_15_all.deb
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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt <[EMAIL PROTECTED]> (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 [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 7 Jun 2005 12:11:48 +0200
Source: postgresql-common
Binary: postgresql-common
Architecture: source all
Version: 15
Distribution: unstable
Urgency: low
Maintainer: Martin Pitt <[EMAIL PROTECTED]>
Changed-By: Martin Pitt <[EMAIL PROTECTED]>
Description:
postgresql-common - manager for PostgreSQL database clusters
Closes: 157282 167864 201702 224047 229240 232553 241337 247261 277700 279184
282803 300896 303259 303274 305347 305427 305724 305912 306836 308589 308597
310716 311546 312298
Changes:
postgresql-common (15) unstable; urgency=low
.
* First unstable upload, welcome to the PostgreSQL future.
* Quiet maintenance:
- pg_maintenance: Supply -q to vacuumdb unless in verbose mode.
- postgresql-common.cron.d: Direct stdout to /dev/null.
- Adapted tests/060_maintenance expected output.
- Closes: #312298
.
postgresql-common (14) experimental; urgency=low
.
* pg_ctlcluster: Check whether mutually exclusive log_*_stats are enabled
to avoid the "FATAL: invalid cache id: 30" error on client invocations.
* Added test 110_invalid_conf: test checking of invalid configurations.
* Ship test suite in /usr/share/postgresql-common.
* pg_ctlcluster: Fix logging of autovacuum daemon.
* pg_ctlcluster: Check if autovacuum daemon is really running, exit with an
error and print log if not.
.
postgresql-common (13) experimental; urgency=low
.
* pg_createcluster: Add option --start to start the new cluster right after
creating it.
* tests/000_existing_clusters: Check for stale postmaster and pg_autovacuum
processes.
* testsuite:
- Temporarily stop existing servers and move away existing files before
executing the tests.
- Restore the original files after the tests.
* pg_upgradecluster: Check return value of pg_dumpall and psql and fail if
they are not successful.
* pg_createuser: Fix indentation of socket warning.
* pg_upgradecluster: Check if cluster is running, exit with an error if not.
* pg_createcluster: Added option --encoding to override detection from
locale.
* pg_createcluster: Guess default encoding from locale for clusters older
than 8.0 to get the same behaviour as for 8.0.
* debian/control: Conflict to postgresql-7.4 << 1:7.4.8-5 since earlier
versions do not support non-ASCII encodings (due to missing pg_encoding).
* pg_ctlcluster: Check that the cluster owner uid/gid really exist.
Closes: #311546
* pg_lsclusters: Ensure that there is at least one space between the colums.
* Added tests/100_encodings which checks cluster creation and updates
for different encodings and locales.
* pg_upgradecluster: Preserve socket directory, locales, and encoding.
* tests/100_encodings: Check the locale the postmaster is running under.
.
postgresql-common (12) experimental; urgency=low
.
* pg_ctlcluster: Remove "status" command, it's not documented and not
really useful.
* PgCommon: Fix cluster_info for avac_logfile to make pg_dropcluster clean
away the autovacuum log file.
* pg_maintenance: -v only influences vacuumdb output now, always show
clusters.
* Added a test suite:
- Test scripts are in tests/*.
- Expected output is in tests/*.ex.
- Test suite is run with './testsuite' as root.
* pg_createcluster:
- Converted optional third parameter to option --datadir.
- Rework POD to have a separate OPTIONS section.
- Add option description to online help.
* pg_ctlcluster: Improve POD.
* pg_upgradecluster:
- Initial framework for handling obsolete configuration parameters.
- Handle transition of {tcpip_socket, virtual_host} -> listen_addresses.
* debian/init.d-functions: If /lib/lsb/init-functions is available, use LSB
init script functions.
* pg_ctlcluster: After start, check whether the cluster is really running.
If it does not come up after 5 seconds, fail and print the recent log
portion.
.
postgresql-common (11) experimental; urgency=low
.
* pg_ctlcluster: Cleaned up variables.
* Factored out change_ugid() to PgCommon.pm and use it in the scripts.
* Added pg_maintenance(8) program.
* Activated formerly disabled postgresql-common.cron.d which calls
pg_maintenance.
* pg_createcluster: Default to cluster owner 'postgres' if no owner is
specified.
* pg_ctlcluster: Fix pg_controldata output parsing and call pg_controldata
under locale 'C' to work with all locales. Closes: #310716
* pg_createcluster: Added --socket-dir option.
* PgCommon.pm: Fix declaration of @lines in set_conf_value() to avoid
duplicating the lines in configuration files.
* PgCommon.pm: Converted to use strict to avoid future errors.
* pg_maintenance: Removed option '-e' from vacuumdb call (leftover from
debugging).
* PgCommon.pm, user_cluster_map(): If several clusters exist, but no
mapping is configured, return not only the default port's cluster version,
but also its name. This fixes the socket directory determination for this
case.
* debian/rules: Fix clean target to remove the manpages created from POD
again.
* pg_upgradecluster: Provide socket directory arguments to psql and
pg_dumpall to make it work for sockets which are not in /tmp.
.
postgresql-common (10) experimental; urgency=low
.
* pg_ctlcluster: Supply cluster socket directory to pg_autovacuum.
.
postgresql-common (9) experimental; urgency=low
.
* Add README.Debian with some general introduction, "first steps for the
impatient", and pointers to further documentation.
* pg_ctlcluster: Check validity of postmaster locale before setting it.
* pg_createcluster: Check validity of locale before calling initdb under it.
* pg_wrapper: Support PGCLUSTER environment variable. Closes: #305912
* pg_upgradecluster:
- Copy original configuration files.
- Configure the target cluster to use the original port, move the old
cluster to a previously unused port.
- Start the new cluster after upgrade.
* debian/init.d-functions: Create /var/run/postgresql if it does not exist.
* pg_createcluster: Set the socket directory to /var/run/postgresql for
postgres-owned clusters. Print a warning to change the directory for other
owners. Closes: #308597
* pg_wrapper: If PGHOST is not defined, set it to the cluster's socket
directory to make client programs work with non-default socket
directories.
.
postgresql-common (8) experimental; urgency=low
.
* pg_ctlcluster: Check whether owner is in the shadow group, and keep shadow
group privilege in this case; this is a poor workaround for Perl's lack of
an initgroups() functions. Closes: #305427
* debian/postgresql-common.postinst: Fix adduser invocation, set home
directory to /var/lib/postgresql. Closes: #308589
* Remove pg_default.1 and pg_exec.1, these programs do not exist. Closes:
#305724
* debian/postgresql-common.links: Add a symlink postgresql-common(7) to
pg_wrapper(1) to make finding the manpage a bit more obvious.
* PgCommon.pm, user_cluster_map(): If there are no clusters, use the latest
version; this makes it possible to use remote clusters with no local ones.
Closes: #306836
.
postgresql-common (7) experimental; urgency=low
.
* Fix warning when calling pg_wrapper with an invalid cluster.
* PgCommon.pm, user_cluster_map(): If only one cluster exists, return that
if no match is found in the map files.
* pg_ctlcluster: Start the postmaster under the locale that was used with
initdb.
* Updated documentation in architecture.html.
.
postgresql-common (6) experimental; urgency=low
.
* pg_dropcluster: Check if postmaster and autovacuum log file paths are
defined before unlinking them to avoid a warning. Closes: #303259
* pg_ctlcluster: Documented the autovacuum stuff in the POD.
* debian/init.d-functions: Add autovacuum commands.
* debian/maintscripts-functions: (Re)start/stop autovacuum daemons on
configuration/removal of p-contrib-*.
* pg_ctlcluster, autovacuum_start(): Check for already running daemon before
starting a new one.
* pg_createcluster: Add an explicit "local all" entry for the database
superuser to pg_hba.conf. Closes: #303274
.
postgresql-common (5) experimental; urgency=low
.
* PgCommon.pm: Internalize get/set_conf_value, export get/set_cluster_port
instead.
* pg_ctlcluster: Integrated pg_autovacuum startup if -contrib is installed
(based on some patches from Adam R. Skutt, thanks).
* pg_createcluster: Create autovacuum_log symlink and log file.
* pg_dropcluster: Remove autovacuum_log symlink and log file.
* PgCommon.pm: If a configuration file is not found in the cluster conf dir,
fall back to the one in /etc/postgresql-common.
* Install /etc/postgresql-common/autovacuum.conf as a fallback default
configuration file for pg_autovacuum.
.
postgresql-common (4) experimental; urgency=low
.
* pg_upgradecluster: Uncomment library search path (artifact from
debugging).
* debian/postgresql-common.postinst: Don't create postgres user with home /,
this can lead to problems sometimes.
* pg_ctlcluster: Fixed pg_ctl invocation (dangling -o argument with versions
< 8.0, caused errors when using dash as /bin/sh). Closes: #300896
.
postgresql-common (3) experimental; urgency=low
.
* Add richer set of common maintainer scripts functions (for package
removal, and also for client and contrib packages).
* Use alternatives system to link manpages from
/usr/share/postgresql/<version>/man/... to /usr/share/man.
.
postgresql-common (2) experimental; urgency=low
.
* pg_wrapper: Check that specified cluster actually exists.
* Fix some Perl warnings.
* Added initial version of pg_upgradecluster(8).
.
postgresql-common (1) experimental; urgency=low
.
* New package to provide a common infrastructure for different PostgreSQL
versions. This finally fixes all bugs concerning failed automatic
upgrades. Closes: #277700, #282803, #224047, #229240, #232553, #279184,
#241337, #247261, #157282, #167864, #305347
* pg_wrapper now has a central role for mapping clients to clusters, so it
is not "overkill" any more. Closes: #201702
Files:
8a66d5c927d3afc8b52ac403d0abeca1 578 misc optional postgresql-common_15.dsc
95bf86d7c6e99b103378cc3e5f732a05 37104 misc optional
postgresql-common_15.tar.gz
f78d86304edb77f0bde0e6b73a5b9b53 56592 misc optional
postgresql-common_15_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCpXMrDecnbV4Fd/IRAtFqAKD22pqyPW6QdqziLTupztvKvwRIbACfVcI7
mFEEGWQkUQabbicbeLrAEM0=
=U5XA
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
