Re: [Bacula-users] Catastrophic changes to PostgreSQL 8.4

From: Eitan Talmi <eitant(at)gmail(dot)com>
To: Avi Rozen <avi(dot)rozen(at)gmail(dot)com>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org, bacula-devel <bacula-devel(at)lists(dot)sourceforge(dot)net>, Kern Sibbald <kern(at)sibbald(dot)com>, bacula-users <bacula-users(at)lists(dot)sourceforge(dot)net>
Subject: Re: [Bacula-users] Catastrophic changes to PostgreSQL 8.4
Date: 2009-12-03 14:48:59
Message-ID: 10dcacc80912030648v272982b6r1a3bb1fb68a719db@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Hi Avi

Please have a look at this link, this is how to install Bacula with MYSQL
database with Hebrew support

Eitan

On Thu, Dec 3, 2009 at 12:35 PM, Avi Rozen <avi(dot)rozen(at)gmail(dot)com> wrote:

> Craig Ringer wrote:
> > Kern Sibbald wrote:
> >
> >> Hello,
> >>
> >> Thanks for all the answers; I am a bit overwhelmed by the number, so I
> am
> >> going to try to answer everyone in one email.
> >>
> >> The first thing to understand is that it is *impossible* to know what
> the
> >> encoding is on the client machine (FD -- or File daemon). On say a
> >> Unix/Linux system, the user could create filenames with non-UTF-8 then
> switch
> >> to UTF-8, or restore files that were tarred on Windows or on Mac, or
> simply
> >> copy a Mac directory. Finally, using system calls to create a file, you
> can
> >> put *any* character into a filename.
> >>
> >
> > While true in theory, in practice it's pretty unusual to have filenames
> > encoded with an encoding other than the system LC_CTYPE on a modern
> > UNIX/Linux/BSD machine.
> >
>
> In my case garbage filenames are all too common. It's a the sad
> *reality*, when you're mixing languages (Hebrew and English in my case)
> and operating systems. Garbage filenames are everywhere: directories and
> files shared between different operating systems and file systems, mail
> attachments, mp3 file names based on garbage id3 tags, files in zip
> archives (which seem to not handle filename encoding at all), etc.
>
> When I first tried Bacula (version 1.38), I expected to have trouble
> with filenames, since this is what I'm used to. I was rather pleased to
> find out that it could both backup and restore files, regardless of
> origin and destination filename encoding.
>
> I like Bacula because, among other things, it can take the punishment
> and chug along, without me even noticing that there was supposed to be a
> problem (a recent example: backup/restore files with a negative mtime ...)
>
> My 2c
> Avi
>
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Bacula-users mailing list
> Bacula-users(at)lists(dot)sourceforge(dot)net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-12-03 15:03:10 Re: numeric cast oddity
Previous Message David Boreham 2009-12-03 14:42:09 Re: Unexpected EOF on client connection

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-12-03 15:09:17 Re: pg_attribute.attnum - wrong column ordinal?
Previous Message toto toto 2009-12-03 14:44:18 I need some help from you