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

mistakes in postgresql-snapshots (7.3)

From: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>
To: pgsql-bugs(at)postgresql(dot)org
Subject: mistakes in postgresql-snapshots (7.3)
Date: 2002-08-05 16:39:36
Message-ID: Pine.LNX.4.44.0208051826440.23455-100000@kix.fsv.cvut.cz (view raw or flat)
Thread:
Lists: pgsql-bugs
Hello,

I tryed postgresql7.3. I install databse on clean redhat with 
--enable-recode --enable-multibyte --enable-nls. I have two questions. 

1. parametr -E encoding of createdb haven't any efect. 
createdb aopk -ELATIN2
CREATE
COMMENT
psql -l
...
aopk      |stehule|SQL_ASCII
If I created db via SQLcmd CREATE DATABASE aopk WITH encoding = 'LATIN2', 
then databese is created with encoding LATIN2, but if databese is with 
encoding other than SQL_ASCII, than I can't use SET CLIENT_ENCODING = 
'WINDOWS1250'. I get error ERROR: Conversion between windows1250 and 
LATIN2 is not supported. When database has def. encoding SQL_ASCII, I can 
use cmd SET CLIENT_ENCODING. Why?

2. I can't as owner of database create functions in plpgsql. Implicit 
triggers are ok. With my function I get message ERROR: plpgsql: permission 
denied. Again, why? What is a new, and what I forgot set.

Bye

Pavel


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2002-08-05 17:02:17
Subject: Re: mistakes in postgresql-snapshots (7.3)
Previous:From: Bruce MomjianDate: 2002-08-04 19:27:32
Subject: Re: Bug #730: cannot create functional index

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