Re: [HACKERS] 6.5 Features list

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] 6.5 Features list
Date: 1999-03-20 02:04:24
Message-ID: 199903200204.LAA01080@ext16.sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> Here is Oleg Bartunov not Oleg Broytman :-)

Wao. Is Oleg a pupular first name?

> Several months ago we discussed
> cyrillic support with mb code, but I was too busy and thanks to Oleg Broytmann
> who kindly agreed to communnicate with you. Short question:
> Will ALTER TABLE has support for changing of encoding for existing
> data ?

No. The backend encoding can be defined for each database but not for
each table. To have a different encoding for each table, we need an
encoding/chaset attribute in the pg_class table. Someday I would try
this (probably with support for NATIONAL CHARACTER).

Is this a serious issue for you?

> Not really difficulties but your mb support is an elegant and flexible way to
> do on-fly encoding support. rcode requires some fixed pre-configuration
> based on host/net definitions.

Thanks for choosing MB support.

BTW, mb(multi-byte support) may not be a suitable naming, since
cyrillic is definitely a single byte encoding:-)
---
Tatsuo Ishii

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-03-20 02:07:01 Re: [HACKERS] aggregation memory leak and fix
Previous Message Bruce Momjian 1999-03-20 02:03:42 Re: [HACKERS] aggregation memory leak and fix