[Dbconfig-common-devel] Bug#463100: bacula-director-pgsql: crash cause memory leak?
sean finney
seanius at debian.org
Tue Jan 29 18:47:59 UTC 2008
hi guys,
yes, dbconfig-common creates a backup of the database before upgrading it.
i'd swear at some point it was on my list to make it optional or
configurable, but i don't think that's been done. the tail of the culprit is
in /usr/share/dbconfig-common/dpkg/postinst (search for "backup before we
upgrade"), and can be dug up from that point.
i'm open to suggestions for how to make this better, ex: debconf questions,
configuration options, implementation details, etc. also, if you have a
less-memory-consuming dump command than what is being currently used, please
do suggest it.
sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20080129/8685ae34/attachment.pgp
More information about the Dbconfig-common-devel
mailing list