mistakes in postgresql-snapshots (7.3) - Mailing list pgsql-bugs

From Pavel Stehule
Subject mistakes in postgresql-snapshots (7.3)
Date
Msg-id Pine.LNX.4.44.0208051826440.23455-100000@kix.fsv.cvut.cz
Whole thread Raw
In response to Bug #650: using a trigger like a sequence doesn't work  (pgsql-bugs@postgresql.org)
Responses Re: mistakes in postgresql-snapshots (7.3)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: mistakes in postgresql-snapshots (7.3)  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List 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

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Bug #730: cannot create functional index
Next
From: Tom Lane
Date:
Subject: Re: mistakes in postgresql-snapshots (7.3)