Your message dated Tue, 23 Aug 2005 15:17:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#318928: fixed in postgresql-common 24
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; 18 Jul 2005 17:31:58 +0000
>From [EMAIL PROTECTED] Mon Jul 18 10:31:58 2005
Return-path: <[EMAIL PROTECTED]>
Received: from cassarossa.samfundet.no [129.241.93.19]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1DuZTC-0005Ay-00; Mon, 18 Jul 2005 10:31:58 -0700
Received: from trofast.ipv6.sesse.net ([2001:700:300:dc03:20e:cff:fe36:a766]
helo=trofast.sesse.net)
by cassarossa.samfundet.no with esmtp (Exim 4.50)
id 1DuZT5-0005Xa-UE; Mon, 18 Jul 2005 19:31:52 +0200
Received: from sesse by trofast.sesse.net with local (Exim 3.36 #1 (Debian))
id 1DuZT4-0005Fo-00; Mon, 18 Jul 2005 19:31:50 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Steinar H. Gunderson" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: postgresql-8.0: should warn if disk cache is enabled
X-Mailer: reportbug 3.15
Date: Mon, 18 Jul 2005 19:31:50 +0200
Message-Id: <[EMAIL PROTECTED]>
X-Spam-Score: -2.8 (--)
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-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: postgresql-8.0
Severity: wishlist
As discussed on Debconf5:
postgres' postinst (or perhaps startup script) should warn if the data
resides on a disk with write cache enabled (use hdparm?), as that can
have potentially disastreous effects on your data integrity (unless
you'd be lucky enough to have battery-backed write cache, which normally
only exists on expensive hardware RAID cards).
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.8
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
---------------------------------------
Received: (at 318928-close) by bugs.debian.org; 23 Aug 2005 22:23:34 +0000
>From [EMAIL PROTECTED] Tue Aug 23 15:23:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1E7h4y-0007N3-00; Tue, 23 Aug 2005 15:17:12 -0700
From: Martin Pitt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#318928: fixed in postgresql-common 24
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 23 Aug 2005 15:17:12 -0700
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-Level:
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-CrossAssassin-Score: 4
Source: postgresql-common
Source-Version: 24
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_24.dsc
to pool/main/p/postgresql-common/postgresql-common_24.dsc
postgresql-common_24.tar.gz
to pool/main/p/postgresql-common/postgresql-common_24.tar.gz
postgresql-common_24_all.deb
to pool/main/p/postgresql-common/postgresql-common_24_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, 23 Aug 2005 23:10:09 +0200
Source: postgresql-common
Binary: postgresql-common
Architecture: source all
Version: 24
Distribution: unstable
Urgency: low
Maintainer: Martin Pitt <[EMAIL PROTECTED]>
Changed-By: Martin Pitt <[EMAIL PROTECTED]>
Description:
postgresql-common - manager for PostgreSQL database clusters
Closes: 316100 318928 320810 323878 324749
Changes:
postgresql-common (24) unstable; urgency=low
.
* Add /usr/share/postgresql-common/pg_checksystem: Check system parameters
which are relevant to PostgreSQL. Right now this checks if write caching
is enabled on any disk containing PostgreSQL clusters.
* debian/postgresql-common.postinst: Call pg_checksystem. Closes: #318928
* Bump Standards-Version to 3.6.2.
* debian/postgresql-common.postinst: Setup user 'postgres' with /bin/bash as
default shell. Closes: #320810
* pg_wrapper, debian/postgresql-common.links: Wrap reindexdb, it is a
standard client program in 8.1.
* pg_createcluster: Do not create autovacuum log file for servers >= 8.1.
* PgCommon.pm: For determining avac_enable on 8.1+ servers, read
"autovacuum" setting from postgresql.conf.
* pg_maintenance: Use avac_enable flag instead of checking for the
pg_autovacuum pid file to determine whether autovacuuming is enabled. This
is a more general approach and works for all server versions.
* pg_ctlcluster: Do not attempt to start pg_autovacuum on 8.1+ servers.
* pg_createcluster: Add hook for version specific function to configure
postgresql.conf.
* pg_createcluster: Add default configuration for 7.4 clusters:
- tcpip_socket = true
- stats_row_level = true
* pg_createcluster: Add default configuration for 8.0 clusters:
- listen_addresses = '*'
- stats_row_level = true
* pg_createcluster: Add default configuration for 8.1 clusters:
- listen_addresses = '*'
- stats_row_level = on
- autovacuum = on
* PgCommon.pm, set_conf_value(): Preserve comments.
* debian/postgresql-common.postinst: Generalized restarting of all clusters
to make it automatically work for future versions.
* pg_createcluster: Adapt pg_hba.conf to the current default (md5 for host
connections, ident sameuser for local ones); this obsoletes the
default-pg_hba.conf patches in the server packages.
* user_clusters: Update comments, throw out bogus documentation.
Closes: #324749
* pg_createcluster: Only mangle configuration files (pg_hba.conf, SSL
enabling, etc.) if we create a new cluster, not if we integrate an already
existing one. Closes: #323878
* Add debian/postgresql-common.logrotate: Simple log rotation.
Closes: #316100
Files:
89dffd1b55cb4f01a2c8c836e7255980 578 misc optional postgresql-common_24.dsc
303931e54070b49253157cd12cac0291 50728 misc optional
postgresql-common_24.tar.gz
4ccd2f68e63191595fefc5dd93ffec12 72168 misc optional
postgresql-common_24_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDC5wKDecnbV4Fd/IRAusEAKC9K9Jo+D80C63gb23PWXLuHhiPRACfZFQc
CADYnX0F4RsaCFG+ukT86k0=
=9mNF
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
