| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | "Arulappan, Arul Shaji" <arul(at)fast(dot)au(dot)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal - Support for National Characters functionality |
| Date: | 2013-07-05 18:35:32 |
| Message-ID: | CAFj8pRBdqbq-VvYbBLXSfaKgdXVGrh==_XtTA63o+_Y1YU=Gig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Yes, what I know almost all use utf8 without problems. Long time I didn't
see any request for multi encoding support.
Dne 5.7.2013 20:28 "Peter Eisentraut" <peter_e(at)gmx(dot)net> napsal(a):
> On 7/4/13 10:11 PM, Arulappan, Arul Shaji wrote:
> > The main aim at the moment is to get some feedback on the above to know
> > if this feature is something that would benefit PostgreSQL in general,
> > and if users maintaining DBs in non-English speaking regions will find
> > this beneficial.
>
> For European languages, I think everyone has moved to using Unicode, so
> the demand for supporting multiple encodings is approaching zero. The
> CJK realm might have difference requirements.
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-07-05 18:47:06 | Preventing tuple-table leakage in plpgsql |
| Previous Message | ivan babrou | 2013-07-05 18:31:12 | Re: Millisecond-precision connect_timeout for libpq |