gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Postgres 8.4.4-1 (Enterprise db) problems -- system


From: Dave Cramer
Subject: Re: [Gnumed-devel] Postgres 8.4.4-1 (Enterprise db) problems -- system hosed?
Date: Thu, 1 Jul 2010 06:13:59 -0400

On Thu, Jul 1, 2010 at 5:58 AM, Sebastian Hilbert
<address@hidden> wrote:
> Am Donnerstag 01 Juli 2010, 11:46:12 schrieb Jim Busser:
>> On 2010-07-01, at 2:16 AM, Sebastian Hilbert wrote:
>> > If you have a chance and still the en_CA local installed please report
>> > what
>> >
>> > psql -l is reporting.
>> >
>> > I wonder if there is a way to find out if en_CA is utf8 and not fail in
>> > the bootstrapper.
>>
>> MacBook:/ djb$ sudo su postgres
>> Password:
>> bash-3.2$ psql -l
>> Password:
>>                               List of databases
>>    Name    |  Owner   | Encoding | Collation | Ctype |   Access privileges
>> -----------+----------+----------+-----------+-------+---------------------
>> -- postgres  | postgres | UTF8     | en_CA     | en_CA |
>>  template0 | postgres | UTF8     | en_CA     | en_CA | =c/postgres
>>
>>                                                      : postgres=CTc/postgre
>>                                                      : s
>>
>>  template1 | postgres | UTF8     | en_CA     | en_CA | =c/postgres
>>
>>                                                      : postgres=CTc/postgre
>>                                                      : s
>>
>> (3 rows)
>>
> In that case it would have been safe to continue. Maybe we can make use of
> this information as well.
>
> If we parse psql -l or have some other way to get the encoding this would let
> us continue even if we have the above situation.
>
> Sebastian
>
> _______________________________________________
> Gnumed-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnumed-devel
>

Couple of things here.....

The binary is being created by edb, not the PG community.

By default pg 8.4 is utf-8, encoding. Any other encoding besides 'C'
is slower. Take that for whatever it's worth.

It's been my experience that en_CA is poorly supported due to the
proximity to our neighbours. I tend to avoid it.

Jim, 8.4 now has the ability to set the encoding of individual
databases when they are created so perhaps we can put that into gnumed
instead of relying on initdb?

My 2 cents worth

Dave



Dave



reply via email to

[Prev in Thread] Current Thread [Next in Thread]