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

Re: [HACKERS] Problems in 6.5.3 with Multi-Byte encoding

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
Cc: pgsql-bugs(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org, 50388(at)bugs(dot)debian(dot)org
Subject: Re: [HACKERS] Problems in 6.5.3 with Multi-Byte encoding
Date: 1999-11-30 03:17:28
Message-ID: 199911300317.WAA25318@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Anyone want to comment on this?  BIG5 anyone?

> With PostgreSQL compiled with support for locales and multi-byte encoding:
> 
> initdb -e BIG5
> 
> [start postmaster]
> psql template1
> \dS causes a segmentation fault in the backend
> 
> >From the log:
> 
> StartTransactionCommand
> query: SELECT usename, relname, relkind, relhasrules FROM pg_class, pg_user 
> WHERE usesysid = relowner and ( relkind = 'r' OR relkind = 'i' OR relkind = 
> 'S') and relname ~ '^pg_' and (relkind != 'i' OR relname !~ '^xinx') ORDER BY 
> relname
> ProcessQuery
> /usr/lib/postgresql/bin/postmaster: reaping dead processes...
> /usr/lib/postgresql/bin/postmaster: CleanupProc: pid 294 exited with status 11
> 
> 
> This can be isolated to the pattern-matching operator:
> 
> template1=> select * from pg_class where relname ~ '^pg_' ;
> pqReadData() -- backend closed the channel unexpectedly.
> 
> ------- Forwarded Message
> 
> Date:    Thu, 18 Nov 1999 19:48:39 +0800
> From:    Chuan-kai Lin <cklin(at)oink(dot)cc(dot)ntu(dot)edu(dot)tw>
> To:      Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
> Subject: Re: Bug#50388: Backend close client-server channel unexpectedly
> 
> On Thu, Nov 18, 1999 at 09:18:34AM +0000, Oliver Elphick wrote:
> > Something must have happened to the database as it was being created.
> > At the moment, I would put it down to cosmic rays or something.
> 
> Through a friend who specializes in metaphysics and astronomy, I
> have traced down the exact cause of our problem: PostgreSQL does
> not like BIG5 encoding.  If you supply "-e BIG5" to initdb, the
> resulting database will be hosed.  Plain and simple.
> 
> This looks like a tough one... somebody better notify the upstream
> developers about this.
> 
> - -- Chuan-kai Lin
> 
> 
> ------- End of Forwarded Message
> 
> 
> -- 
>       Vote against SPAM: http://www.politik-digital.de/spam/
>                  ========================================
> Oliver Elphick                                Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
> Isle of Wight                              http://www.lfix.co.uk/oliver
>                PGP key from public servers; key ID 32B8FAA1
>                  ========================================
>      "To show forth thy lovingkindness in the morning, and 
>       thy faithfulness every night."     Psalms 92:2 
> 
> 
> 
> ************
> 


-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist(at)candle(dot)pha(dot)pa(dot)us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1999-11-30 03:28:45
Subject: Re: [HACKERS] Re: [PATCHES] A bag of psql goodies
Previous:From: Bruce MomjianDate: 1999-11-30 03:11:06
Subject: Re: [HACKERS] Status of sql_help.h

pgsql-bugs by date

Next:From: Tatsuo IshiiDate: 1999-11-30 04:43:27
Subject: Re: [HACKERS] Problems in 6.5.3 with Multi-Byte encoding
Previous:From: Bruce MomjianDate: 1999-11-30 02:28:28
Subject: Re: A bug in NOT IN (SELECT ...

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