[pkg-bacula-devel] The database update
Sven Hartge
sven at svenhartge.de
Tue Jan 23 16:46:41 GMT 2024
On 22.01.24 12:58, Carsten Leonhardt wrote:
> the current state in the experimental branch is that I've successfully
> upgraded a simple test installation of bacula using postgresql from
> stable to experimental. A backup done before the update could be
> restored successfully after the update.
>
> I didn't have time for further tests yet.
>
> I also wonder why the people at Bacula chose the dump/restore route when
> there are builtin commands that have the same effect. Maybe to save disk
> space?
Maybe.
On MySQL/MariaDB an ALTER TABLE needs basically the same space of the
affected table again, because for InnoDB it internally does the
equivalent of "CREATE TEMP TABLE; SELCECT * FROM source; RENAME TABLE;
For example on MariaDB my File table of 220GB size dumps into an ~120GB
SQL file, so dumping and restoring would save about 100GB of space.
(Which will pose a problem for me once the upgrade to 11++ comes around,
because /var/lib/mysql is about 78% percent full and for neither
dumping nor ALTER TABLE is there enough space.)
Grüße,
Sven.
More information about the pkg-bacula-devel
mailing list