| From: | Marc Cuypers <m(dot)cuypers(at)mgvd(dot)be> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: upgrade from 7.4 to 8.3 |
| Date: | 2009-03-11 12:40:38 |
| Message-ID: | 49B7B146.8010204@mgvd.be |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Gregory Stark schreef:
> Marc Cuypers <m(dot)cuypers(at)mgvd(dot)be> writes:
>
>> Error:
>> ERROR: encoding LATIN9 does not match server's locale nl_BE.utf8
>> SQL state: XX000
>> Detail: The server's LC_CTYPE setting requires encoding UTF8.
>>
>> Can i only use nl_BE and UTF-8 now?
>> Why can't i use LATIN9 anymore?
>> Is bacula 8.3 stricter in this respect to 7.4?
>
> 8.3 is stricter about checking that the configuration makes sense. But even
> under 7.4 you would have had problems, you just wouldn't have been forewarned
> so soon. You would still only be able to use nl_BE.utf8 collation but you
> would have been allowed to tell the server your data was encoded with latin9.
> So the collation results would have been nonsensical. Ie, comparisons like <
> and > would have given incorrect results.
>
> If this database is still under development and your schedule allows one
> option might be use 8.4dev from CVS. It should be released sometime in the
> next 3-6 months and will allow you to have a different encoding and locale for
> each database.
I'd like to stay with the standard version of debian. So 8.4 is not an
option.
But i'll convert the database in 7.4 to UTF-8. So the problem will be
solved.
--
Marc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-03-11 12:47:21 | Re: upgrade from 7.4 to 8.3 |
| Previous Message | Marc Cuypers | 2009-03-11 12:38:19 | Re: SOLVED upgrade from 7.4 to 8.3 |