Skip site navigation (1) Skip section navigation (2)

Re: BUG #5345: non-administrator users cannot create databases with special encoding

From: Kovács Zoltán <kovzol(at)particio(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5345: non-administrator users cannot create databases with special encoding
Date: 2010-02-25 07:30:19
Message-ID: e47fa2b61002242330r135e8f50p4b9f494d151e32d@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Dear Tom, thank you for the explanation.

2010/2/24 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>

> "Zoltan Kovacs" <kovzol(at)particio(dot)com> writes:
> > I would like to create a database using SQL_ASCII encoding, but it is not
> > allowed for a normal user, only for the postgres user.
>
> There is an exception that will allow superusers to do that, but it's
> not a good idea for them either.  The problem is not the encoding per
> se, it's that it's unsafe in combination with a locale setting that
> assumes UTF8.  The only safe locale for SQL_ASCII is C.
>
> If you want to have one database that is C/SQL_ASCII and others that
> have different locale settings, you need to upgrade to PG 8.4.  8.3
> can only have one locale across the entire installation.
>

Yes, this is the case for me.

What can happen if I use an unsafe combination? Can the backend unexpectedly
die? Can this cause data corruption?

Thank you for your answer in advance.

Best regards, Zoltan


>
>                        regards, tom lane
>

In response to

Responses

pgsql-bugs by date

Next:From: Wappler, RobertDate: 2010-02-25 08:47:20
Subject: Re: helo
Previous:From: Toni HeleniusDate: 2010-02-25 06:58:53
Subject: Re: BUG #5338: PG_DUMP fails due to invalid adnum value

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group