Hi Eric Thanks for the tip. The files that are causing me grief are old files which Bacula/PostgreSQL used to handle OK. My client is UTF8 these days, but these files are remnants which were originally created as MacRoman. I must confess I can't remember definitively what encoding I was using in the old PostgreSQL database before the upgrade, but I thought it was UTF8. I certainly want to work with UTF8 in the future, though if SQL_ASCII means effectively "plain uninterpreted binary" it may be worth a closer look.
Steve On 5 Jan 2008, at 13:45, Eric Bollengier wrote: > Hi, > > If your are using PostgreSQL with UTF8, Postgres will check all > input to see if they are valid UTF8. > > If your client is in ISO885X, you will not be able to store filename > with accent in your catalog. > > To be able to store anything, you have to use SQL_ASCII (the name > could be confusing) > > Before Batch mode, only filenames with accent were discarded, now > we use a big transaction, so the whole transaction is aborded. > > You have to convert your database encoding (dump, create, restore). > Or you can also disable batch mode, but it's something like x20 > slower... > > see: > http://www.mail-archive.com/bacula-users%40lists.sourceforge.net/msg26192.html > > Bye > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
