--- Tom Lane <[EMAIL PROTECTED]> wrote:
> It seems risky, but you could probably get away with that as long
> as the database locale (LC_COLLATE/LC_CTYPE) is "C" ... which is really
> the only one that's safe with SQL_ASCII anyway ...
I actually created the cluster with:
test1:~# /usr/lib/postgr
ow <[EMAIL PROTECTED]> writes:
> I see... If *ALL* data is in ASCII, is it possible to just update
> "pg_database.encoding" to UTF-8 or will I need to recreate the db?
It seems risky, but you could probably get away with that as long
as the database locale (LC_COLLATE/LC_CTYPE) is "C" ... which is
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> ow <[EMAIL PROTECTED]> writes:
> > Are there any negative effects related to the selection of UTF-8 over
> SQL_ASCII
>
> There will be a speed penalty; whether it's significant in your
> application is something you can only determine by experiment.
I
ow <[EMAIL PROTECTED]> writes:
> Are there any negative effects related to the selection of UTF-8 over
> SQL_ASCII
There will be a speed penalty; whether it's significant in your
application is something you can only determine by experiment.
regards, tom lane
---
Am Dienstag, 7. März 2006 15:08 schrieb ow:
> Are there any negative effects related to the selection of UTF-8 over
> SQL_ASCII (e.g. size of the database, sort/like/group issues, etc)?
If you're only planning to store ASCII data, choosing UTF-8 will not cause any
additional problems. But obviou
"PostgreSQL 8.1.0 on i486-pc-linux-gnu, compiled by GCC cc (GCC) 4.0.3 2005
(prerelease) (Debian 4.0.2-4)"
Hi,
Am having some doubts whether a new db should be with SQL_ASCII or UTF-8
encoding. We expect ALL of our data to be ASCII. At the same time, I guess,
it's possible that some user may
