Package: postgresql-common
Version: 113
Severity: normal
Hi,
/usr/bin/pg_upgradecluster contains the following code:
# log_statement transition
if (defined $c{'log_statement'}) {
PgCommon::set_conf_value $newversion, $cluster, 'postgresql.conf',
'log_statement', ($c{'log_statement'} ? 'all' : 'none');
}
According to the original commit[1] that introduced this change back in 2005,
this was meant to facilitate transitioning from 7.4 to 8.0, where the semantics
of log_statement changed from {true, false} to {none, all}.
However, during migration from 8.3 to 8.4, if log_statement is defined in the
config, then it seems that this code unconditionally sets log_statement to
"all".
We had this hit us on a lenny -> squeeze transition of a particularly busy
database server, where we had set log_statement to "ddl"; pg_upgradecluster
set log_statement to "all" and we almost lost the database server due to disk
space exhaustion within 10 hours.
Thanks,
Apollon
[1] http://bazaar.launchpad.net/~pitti/postgresql/common/revision/240
-- System Information:
Debian Release: 6.0
APT prefers squeeze-updates
APT policy: (500, 'squeeze-updates'), (500, 'stable'), (90, 'unstable'), (80,
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
