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

BUG #1976: steps to reproduce BUG #1438: Non UTF-8 client encoding problem

From: "Stanislav Sukholet" <ctac113(at)mail(dot)ru>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1976: steps to reproduce BUG #1438: Non UTF-8 client encoding problem
Date: 2005-10-19 02:31:30
Message-ID: 20051019023130.0D4ADF0C4D@svr2.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      1976
Logged by:          Stanislav Sukholet
Email address:      ctac113(at)mail(dot)ru
PostgreSQL version: 7.4.8.1.FC3.1
Operating system:   2.6.12-1.1378_FC3
Description:        steps to reproduce BUG #1438: Non UTF-8 client encoding
problem
Details: 

That was really easy to reproduce:
$ export LANG=ru_RU.koi8r
$ createdb -E UNICODE mydb
$ psql -d mydb
mydb=# \encoding KOI8
mydb=# create table a (aa integer);
CREATE TABLE
mydb=# create table b (bb integer primary key);
ERROR:  ignoring unconvertible UTF-8 character 0xd3cf
mydb=# \d
            
   |  |      | 
--------+-----+---------+----------
 public | a   |  | postgres
(1 )

mydb=#

So, it's always a problem when I put PRIMARY KEY modifier after column
declaration with KOI8 encoding.
I've put this report to bugzilla(at)redhat:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171174

Responses

pgsql-bugs by date

Next:From: UlrikeDate: 2005-10-19 06:38:24
Subject: BUG #1977: Na data in GDV Spatial Commander
Previous:From: Tom LaneDate: 2005-10-19 02:16:54
Subject: Re: Fwd: BUG #1972: index error with space character

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