> 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
