Package: postgresql
Version: 7.4.7-6sarge2
Severity: normal
Tags: patch

If you have PostgreSQL installed, but not started in any
runlevel, then the do.maintenance script will always bail
out, even if the server is in fact running (eg because it
has been started manually).

(Such a configuration might be used, for example, if you
have to manually mount an encrypted /var/lib/postgres/data
partition before the server can be started.)

This results in VACUUM and ANALYZE not being run, causing
gradual performance degradation and eventually could cause
a transaction ID rollover.

Given that do.maintenance already checks in /var/run/postgresql
to ensure that the server is actually running, is there a need
to perform an additional runlevel check?



-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.11.10-p4-4g
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages postgresql depends on:
ii  adduser          3.63                    Add and remove users and groups
ii  debconf [debconf 1.4.30.13               Debian configuration management sy
ii  debianutils      2.8.4                   Miscellaneous utilities specific t
ii  dpkg             1.10.28                 Package maintenance system for Deb
ii  libc6            2.3.2.ds1-22sarge3      GNU C Library: Shared libraries an
ii  libcomerr2       1.37-2sarge1            common error description library
ii  libkrb53         1.3.6-2sarge2           MIT Kerberos runtime libraries
ii  libpam0g         0.76-22                 Pluggable Authentication Modules l
ii  libperl5.8       5.8.4-8sarge4           Shared Perl library
ii  libpq3           7.4.7-6sarge2           PostgreSQL C client library
ii  libreadline4     4.3-11                  GNU readline and history libraries
ii  libssl0.9.7      0.9.7e-3sarge1          SSL shared libraries
ii  mailx            1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii  postgresql-clien 7.4.7-6sarge2           front-end programs for PostgreSQL
ii  procps           1:3.2.1-2               The /proc file system utilities
ii  python2.3        2.3.5-3sarge1           An interactive high-level object-o
ii  ucf              1.17                    Update Configuration File: preserv
ii  zlib1g           1:1.2.2-4.sarge.2       compression library - runtime

-- debconf information:
* postgresql/initdb/location: /var/lib/postgres/data
  postgresql/upgrade/preserve_location: $PGDATA/..
* postgresql/settings/day_month_order: European
  postgresql/upgrade/policy: true
* postgresql/settings/locale: C
  postgresql/enable_lang: true
* postgresql/purge_data_too: false
  postgresql/very_old_version_warning: true
  postgresql/upgrade/dump_location: $PGDATA/..
  postgresql/convert-pg_hba.conf: true
--- do.maintenance.old  2006-06-19 11:29:28.000000000 +0100
+++ do.maintenance      2006-06-19 11:31:47.000000000 +0100
@@ -53,14 +53,6 @@
 
 . /etc/postgresql/postgresql.env
 
-/usr/sbin/invoke-rc.d --query postgresql start
-if [ $? -ne 104 ]
-then
-       [ -n "$verbose" ] && 
-               echo "PostgreSQL is currently disabled by update-rc.d or 
file-rc"
-       exit 1
-fi
-
 if [ ! -S /var/run/postgresql/.s.PGSQL.5432 ]
 then
        [ -n "$verbose" ] && 

Reply via email to