In response to "Roland Roberts" <[EMAIL PROTECTED]>: > > Bill Moran wrote: > > > Connect to the PostgreSQL database using the psql command: > > psql -U bacula bacula > > > > Then enter "\l" to list the installed databases and their attributes. You > > should see the bacula database as UTF8. > > > The database is UTF8; all the databases on this host are UTF8. > > > To see what the client encoding is, you can do "show client_encoding;" from > > the psql program. If this is not set to UTF8, you _can_ change it on the > > fly. Simply issue "ALTER DATABASE bacula SET client_encoding='UTF8';" Then > > you'll want to restart Bacula for it to pick up the new setting. > > Hmm, okay, but it shows UTF8. And shouldn't the bacula client be doing that?
Yes, it _should_. I don't know if it _does_. > Because I'm going on vacation and don't want to leave home without a backup > (especially since the laptop will be used in the field, literally), I ended > up just removing the offending packages. I'll try to play around with this > again after vacation. Well, based on your response, I don't have an explanation for your problem. Perhaps when you return we can track it down. -- Bill Moran http://www.potentialtech.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
