| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | db(at)zigo(dot)dhs(dot)org |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgman(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: locale |
| Date: | 2004-04-07 23:22:37 |
| Message-ID: | 20040408.082237.74752799.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Wed, 7 Apr 2004, Tom Lane wrote:
>
> > If that were so, we'd not have a problem. The reason we have to tread
> > very carefully is that we do not know what tables/indexes users might
> > have added to template1.
>
> Aah, now I see the real problem!
>
> > If we copy a text index into a new database and claim that it is sorted
> > by some new locale, we'd be breaking things.
>
> How is this handled for encodings? You can very well have something in
> template1 in an encoding that is not compatible with the encoding you use
> to create a new database.
Are you talking about the sort order? Then there's no problem with
encoding itself.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dann Corbit | 2004-04-08 00:56:37 | Log reader? |
| Previous Message | Dennis Bjorklund | 2004-04-07 20:55:24 | Re: locale |