bacula-director-pgsql postinst script uses UTF8 to create database instead of SQL_ASCII

Bug #253648 reported by Eric Bollengier
2
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: bacula-director-pgsql

Release: hardy
Version: 2.2.8-5ubuntu7

The postinst script of bacula-director-pgsql package create the bacula postgresql catalog in UTF8.

Bacula doesn't work with a postgresql DB using UFT8 encoding. If users try to backup non-UTF8 files (ISO8859 for example) then postgresql will refuse to insert filename into the database.

This issue is documented on bacula documentation
http://www.bacula.org/en/rel-manual/Installi_Configur_PostgreS.html#SECTION005220000000000000000

To correct this, the package have to dump/drop/create/restore the bacula database.

According to the bacula-director-pgsql.postinst script, the bacula user is allowed to create database. This is not mandatory, and should be avoided.

Regards

-Eric Bollengier

Related branches

Ante Karamatić (ivoks)
Changed in bacula:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bacula - 2.4.2-1ubuntu5

---------------
bacula (2.4.2-1ubuntu5) intrepid; urgency=low

  * Create postgresql database with SQL_ASCII encoding, not
    UTF8 (LP: #253648)

 -- Ante Karamatic <email address hidden> Sat, 27 Sep 2008 10:11:55 +0200

Changed in bacula:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.