Your message dated Thu, 16 Aug 2012 13:04:17 +0200
with message-id <[email protected]>
and subject line Re: Bug#463893: postgresql-8.3: please automate database
upgrade between pgsql releases
has caused the Debian Bug report #463893,
regarding postgresql-8.3: please automate database upgrade between pgsql
releases
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
463893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463893
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-8.3
Version: 8.3~rc2-1+b1
Severity: wishlist
>> Leaving aside the entire undesirability of this manual upgrade procedure,
>
> We could try to upgrade an older cluster to a newer version
> automatically if you have an older one installed. However, this can
> also lead to a lot of troubles, and success is not guaranteed. I could
> add another debconf question about this, though. If you think that
> this would be an important feature, please file a wishlist bug about
> it, and how you think the upgrade should look like. We can then
> discuss there what to do when the disk runs out of space, or the
> upgrade fails, etc.
I think it's important to make all upgrade processes as automatic as possible.
It's these manual interventions which defeat many if not most people.
We need to cater to users of applications who use postgres but who have never
otherwise even heard of it and are unfamiliar with the commandline environment
as well as the system programmers and database gurus.
I think an automatic upgrade with an opportunity to not upgrade (for disk
space, known problems, or whatever) is the way to go.
If any resultant fallout is then addressed the world becomes a better place.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-k7 (SMP w/1 CPU core)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages postgresql-8.3 depends on:
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libcomerr2 1.40.5-2 common error description library
ii libkrb53 1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries
ii libldap-2.4-2 2.4.7-4 OpenLDAP libraries
ii libpam0g 0.99.7.1-5 Pluggable Authentication Modules l
ii libpq5 8.3~rc2-1+b1 PostgreSQL C client library
ii libssl0.9.8 0.9.8g-4 SSL shared libraries
ii libxml2 2.6.31.dfsg-1 GNOME XML library
ii postgresql-client-8.3 8.3~rc2-1+b1 front-end programs for PostgreSQL
ii postgresql-common 84 PostgreSQL database-cluster manage
ii tzdata 2007k-2 time zone and daylight-saving time
postgresql-8.3 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Mark,
Mark Robinson [2008-02-04 14:16 +1300]:
> I think it's important to make all upgrade processes as automatic as
> possible.
> It's these manual interventions which defeat many if not most people.
I think the current system of calling pg_upgradecluster and pointing
this out in a debconf note during dist-upgrade is about as far as we
can go. A database upgrade is nothing that we can ever guarantee to
succeed in a fully automatic fashion.
So this is "wontfix", and I'm closing the report to clean up the bug
tracker a bit.
Thank you!
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
