Hello,
I am the project manager of Bacula. One of the database backends that Bacula
uses is PostgreSQL.
This email is to notify you that a change you made to setting database
character codes has created havoc with certain unfortunate Bacula users.
Bacula sets the database encoding to SQL_ASCI
ers in the database with no character encoding
checks in the future.
See more notes below ...
On Thursday 03 December 2009 03:54:07 Craig Ringer wrote:
> On 2/12/2009 9:18 PM, Kern Sibbald wrote:
> > Hello,
> >
> > I am the project manager of Bacula. One of the database b
> 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
On Thursday 03 December 2009 16:42:58 Adrian Klaver wrote:
> On Wednesday 02 December 2009 11:33:38 pm Kern Sibbald wrote:
> > > ( BTW, one way to handle incorrectly encoded filenames and paths might
> > > be to have a `bytea' field that's generally null to stor
Hello,
Thanks for your response.
On Thursday 03 December 2009 16:46:54 Tom Lane wrote:
> Sam Mason writes:
> > As others have said; BYTEA is probably the best datatype for you to
> > use. The encoding of BYTEA literals is a bit of a fiddle and may need
> > some changes, but it's going to be muc
