Your message dated Mon, 05 Apr 2010 17:24:02 +0000
with message-id <[email protected]>
and subject line Bug#543506: fixed in postgresql-common 106
has caused the Debian Bug report #543506,
regarding postgresql-common: pg_upgradecluster doesn't preserve per-database
ACLs or configuration parameters
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.)
--
543506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543506
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-common
Version: 94lenny1
Severity: normal
pg_upgradecluster doesn't preserve the contents of pg_database.datconfig
or pg_database.datacl.
(That is, it doesn't preserve the results of 'GRANT foo ON DATABASE bar
TO baz' or 'ALTER DATABASE name SET foo TO bar'.)
I think bug 539772 is a specific case of this issue.
This information isn't provided by either pg_dump or pg_dumpall -g. It
is included in the output of pg_dumpall -s, in the 'Database creation'
section.
Possible strategies for implementing this in pg_upgradecluster might be
to parse the information out of the 'pg_dumpall -s' output, or to
duplicate the dumpCreateDB logic from pg_dumpall.
--- End Message ---
--- Begin Message ---
Source: postgresql-common
Source-Version: 106
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-client-common_106_all.deb
to main/p/postgresql-common/postgresql-client-common_106_all.deb
postgresql-common_106.dsc
to main/p/postgresql-common/postgresql-common_106.dsc
postgresql-common_106.tar.gz
to main/p/postgresql-common/postgresql-common_106.tar.gz
postgresql-common_106_all.deb
to main/p/postgresql-common/postgresql-common_106_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.8
Date: Mon, 05 Apr 2010 17:58:25 +0200
Source: postgresql-common
Binary: postgresql-common postgresql-client-common
Architecture: source all
Version: 106
Distribution: unstable
Urgency: low
Maintainer: Martin Pitt <[email protected]>
Changed-By: Martin Pitt <[email protected]>
Description:
postgresql-client-common - manager for multiple PostgreSQL client versions
postgresql-common - PostgreSQL database-cluster manager
Closes: 522679 543506 562676 576180
Changes:
postgresql-common (106) unstable; urgency=low
.
* t/001_packages.t: Check for ".utf8" locale instead of ".UTF-8". This
seems to be the new canonical spelling now.
* t/TestLib.pm, check_clean(): Require that /var/log/postgresql/ still
exists. If we remove it entirely, current versions of logcheck complain
loudly. This was already fixed a while ago in squeeze, this will ensure it
stays so. (Closes: #576180)
* t/040_upgrade.t: Check upgrade of database and table ACL, an ALTER
DATABASE option, and correct upgrading of a custom pg_hba.conf. This
reproduces #543506.
* pg_upgradecluster: Rework logic to use "pg_dumpall -s" instead of
"pg_dumpall -g", to also catch ACLs, global settings, and the like. Drop
manual database creation and encoding special-cases, since those are being
taken care of by the -s commands already. (Closes: #543506, #562676)
* pg_upgradecluster: Re-enable connections after the upgrade is done, not in
between.
* t/120_pg_upgradecluster_scripts.t: Upgrade scripts should not create
tables in the "init" phase, since they will be overwritten during
dump/restore. Change the test case to move table changes into the "finish"
phase, and update documentation in pg_upgradecluster to point out this
potential problem.
* debian/init.d-functions, status(): More appropriate output formatting for
"status" init script commands. (Closes: #522679)
Checksums-Sha1:
94a558c41758a93f81c0c6a19d3ba4d9ce26db74 906 postgresql-common_106.dsc
32a45cc7310b666978d16193042ea0b714d2521b 1643040 postgresql-common_106.tar.gz
1398f0bf05685421c2447603aae3fe9667f71c6e 121214 postgresql-common_106_all.deb
140d946f5016280962863adf431883f6681d0c3a 52008
postgresql-client-common_106_all.deb
Checksums-Sha256:
2abf1ddfb6cf96f775a45adb9b7a06e1f5330d2142e293725f51e5d3c67e1ec0 906
postgresql-common_106.dsc
1112475c0ca6b3fe4bad827cf1bba325ae4c015fcfac9d99005af8181039d3b3 1643040
postgresql-common_106.tar.gz
b8d3dd49230c9cbfc96efc398b5513739215c45f794d42453f97db0eb974b4ac 121214
postgresql-common_106_all.deb
c6249c71e189f1abe83d0247bbb722ea584c4b35ea8de02e9f35e3943073b263 52008
postgresql-client-common_106_all.deb
Files:
afabe91d8d36c143ca0a66743582948a 906 database optional
postgresql-common_106.dsc
fb2e85fff712da6e1eed10761890984a 1643040 database optional
postgresql-common_106.tar.gz
5cf7201e9886be8f0ab10309c5b95ccc 121214 database optional
postgresql-common_106_all.deb
742807eeb526c98ac3a9006d2a85fedd 52008 database optional
postgresql-client-common_106_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAku6CNoACgkQDecnbV4Fd/KIxACfX6mIuRgbPWohZdqocaR1GTCI
XzYAoNxH8cTyhRcB3SJ05dkaMYo0R7Qf
=MbRM
-----END PGP SIGNATURE-----
--- End Message ---
