Re: --enable-locale and SET command ... - Mailing list pgsql-hackers

From Mitch Vincent
Subject Re: --enable-locale and SET command ...
Date
Msg-id 01e601bfb5d7$a337c340$4100000a@venux.net
Whole thread Raw
In response to --enable-locale and SET command ...  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: --enable-locale and SET command ...  (Don Baccus <dhogaza@pacifier.com>)
List pgsql-hackers
Hmm, I guess they're trying to be misleading when they say "Up to 4GB of
memory (PC100 ----> SDRAM <-----)"?

Hmm, there isn't any mention of the nead for RDRAM... Shame on these
companies for trying to screw people.

- Mitch

----- Original Message -----
From: The Hermit Hacker <scrappy@hub.org>
To: <pgsql-hackers@postgresql.org>
Sent: Thursday, May 04, 2000 10:29 AM
Subject: [HACKERS] --enable-locale and SET command ...


>
> Morning ...
>
> Have a client that is asking us to enable localization support so
> that he can deal with turkish characters ... docs seem a bit sparse on
> this (or I'm not looking in the right place), but I'm guessing I want to
> use --enable-locale vs --enable-multibyte? *raised eyebrow*
>
> From the docs for v7.0, found at:
>
> http://www.postgresql.org/users-lounge/7.0/docs/postgres/x16981.htm
>
> It appears that I can't set this on a per-database?  Its the whole
> server?
>
> I've looked at the SET command, but I think that might be where
> I'm missing something ...
>
> Marc G. Fournier                   ICQ#7615664               IRC Nick:
Scrappy
> Systems Administrator @ hub.org
> primary: scrappy@hub.org           secondary:
scrappy@{freebsd|postgresql}.org
>



pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Hardware/CPU Thoughts (Was: Re: system usage stats )
Next
From: Don Baccus
Date:
Subject: Re: system usage stats (Was: Re: Why Not MySQL? )