Your message dated Thu, 16 Aug 2012 12:05:19 +0200
with message-id <[email protected]>
and subject line Re: Bug#613348: postgresql-common: pg_upgradecluster nukes
pg_hba.conf in both old and new clusters
has caused the Debian Bug report #613348,
regarding postgresql-common: pg_upgradecluster nukes pg_hba.conf in both old
and new clusters
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.)
--
613348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613348
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-common
Version: 113
Severity: normal
Hi,
after running pg_upgradecluster to upgrade from 8.3 (Lenny) to 8.4
(Squeeze), my pg_hba.conf in the 8.3 release was nuked, and the
pg_hba.conf in 8.4 is also broken. As a result, all my access controls
are lost, and all database-using applications stopped working.
I see no reason why the program should mangle the old pg_hba.conf in the
first place. The man page also gives no warning whatsoever.
Kind regards,
--Toni++
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages postgresql-common depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii postgresql-client-commo 113 manager for multiple PostgreSQL cl
ii procps 1:3.2.8-9 /proc file system utilities
ii ssl-cert 1.0.28 simple debconf wrapper for OpenSSL
postgresql-common recommends no packages.
postgresql-common suggests no packages.
-- debconf information:
* postgresql-common/obsolete-major:
postgresql-common/untransitioned:
--- End Message ---
--- Begin Message ---
Hello again,
Martin Pitt [2011-10-03 16:04 +0200]:
> Toni Mueller [2011-02-14 10:22 +0100]:
> > after running pg_upgradecluster to upgrade from 8.3 (Lenny) to 8.4
> > (Squeeze), my pg_hba.conf in the 8.3 release was nuked
>
> The evidence is probably long gone, but do you still remember what
> "nuked" meant there? Was it an empty file? No file at all? Was there a
> pg_hba.conf.orig?
>
> > I see no reason why the program should mangle the old pg_hba.conf in the
> > first place. The man page also gives no warning whatsoever.
>
> It's temporarily changed to ensure that only the local superuser has
> access to it during upgrade. I got other bug reports in the past that
> other apps tried to access the DB while the upgrade was running, which
> either disrupted the upgrade or at least led to inconsistencies.
>
> I just looked at the code for creating the backup and temporary
> pg_hba.conf, and it indeed could be made a tad more robust. But I
> don't see how it can create an empty pg_hba.conf without renaming the
> original file as pg_hba.conf.orig first. pg_upgradecluster never
> removes that file, it just uses rename().
>
> Do you happen to have a way to reproduce this?
Without further information there is nothing I can do about this, I'm
afraid. I guess by now any debug evicende is long gone, so I'm closing
this report.
Thanks!
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
