Your message dated Tue, 25 Jul 2006 14:18:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#351571: fixed in postgresql-common 58 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)
--- Begin Message ---Package: postgresql-common Version: 41 Severity: Wishlist Greetings, When using pg_upgradecluster to migrate from 8.0 to 8.1 I ran into some problems. Mainly this was that I had PostGIS installed in the 8.0 database and had some tables with geometry columns which depended upon PostGIS. When pg_upgradecluster created the 8.1 cluster PostGIS wasn't installed (and there doesn't seem to be any way to have PostGIS installed between when the cluster is created and the restore is started). Therefore, I propose that pg_upgradecluster should either have a hook where things can be run between the cluster being created and the restore starting, or it should be able to be run against an existing cluster (so the user could install the necessary components). An associated fun an interesting question is how one might exclude things from the restore. I don't think this is a PostGIS-specific issue but really applies to any module where an object in the database depends on the module being installed. Thanks! Stephen
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Source: postgresql-common Source-Version: 58 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_58_all.deb to pool/main/p/postgresql-common/postgresql-client-common_58_all.deb postgresql-common_58.dsc to pool/main/p/postgresql-common/postgresql-common_58.dsc postgresql-common_58.tar.gz to pool/main/p/postgresql-common/postgresql-common_58.tar.gz postgresql-common_58_all.deb to pool/main/p/postgresql-common/postgresql-common_58_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, 25 Jul 2006 22:34:42 +0200 Source: postgresql-common Binary: postgresql-client-common postgresql-common Architecture: source all Version: 58 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 - manager for PostgreSQL database clusters Closes: 351571 Changes: postgresql-common (58) unstable; urgency=low . * pg_wrapper: Improve manpage POD, describe the precise rules for cluster selection. * t/090_multicluster.t: Check for proper error message of pg_wrapper (no suitable default cluster) if several local clusters exist and none are on the default port. * pg_wrapper: Print proper error message if no cluster is suitable as default target and point to man pg_wrapper. * pg_upgradecluster: - Support /etc/postgresql-common/pg_upgradecluster.d/ hook scripts. These are called after creating the virgin new version cluster (phase 'init') and a second time after the upgrade is complete (phase 'finish'). PostgreSQL extensions like PostGIS can use these hooks to initialize metadata which must not be upgraded from the old cluster, but initialized from scratch. Closes: #351571 - Document this feature in the manpage POD. - If upgrade scripts are present, call pg_restore with the new -X no-data-for-failed-tables option to not clutter already existing tables in the new cluster with data from the old cluster. Abort with an error if the installed pg_restore does not support this option. - debian/postgresql-common.dirs: Ship /etc/postgresql-common/pg_upgradecluster.d/. * Add t/120_pg_upgradecluster_scripts.t: Selftest for pg_upgradecluster.d hooks and proper pg_restore -X no-data-for-failed-tables behaviour. * PgCommon.pm, get_cluster_locales(): Fix parsing of locales out of pg_controldata output by calling it under the locale 'C' and being more liberal in the regular expression. (https://launchpad.net/bugs/50755) Files: f5309c19f58ce0ce0b3d1cfd514670b0 604 misc optional postgresql-common_58.dsc e49dc0e48006c14794ee87fc2a68e647 84438 misc optional postgresql-common_58.tar.gz 8ee03c982f2787b15641d4ccb627f5c2 89912 misc optional postgresql-common_58_all.deb 0186a79d5cead278a2c378bbd9cef77d 36734 misc optional postgresql-client-common_58_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFExob1DecnbV4Fd/IRAhDSAJ97sflhksLoieZsWiagc5s0ZcaEAgCg7Lfa 3YlHczZfXr2wm4JGHDWrxzM= =yS77 -----END PGP SIGNATURE-----
--- End Message ---
