Re: Internationalization - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Internationalization
Date
Msg-id 20040630221025.GI16503@dcc.uchile.cl
Whole thread Raw
In response to Internationalization  (Dennis Gearon <gearond@fireserve.net>)
List pgsql-general
On Wed, Jun 30, 2004 at 02:26:10PM -0700, Dennis Gearon wrote:

> 1/ Make individual databases possible with a single instance that can be
> different encoding AND locale/sorting, and all other aspects of using
> the encoding/langauge rules.

> Is there anyway for a single statement to access more than one database?
> Could a query, regexes, etc be facing indexes in different
> encodings/sorting collations if different databases in a cluster had
> different encodings/collations?

No, but there are at least two problems:

1. shared tables.  All databases in each cluster shared at least
pg_database, pg_shadow, pg_group and (new) pg_tablespace.  And, of
course, all their indexes.  What would you do about them?

2. when creating a new database, the current method is to copy from
template1.  How would you change the encoding of the new database?

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"The problem with the future is that it keeps turning into the present"
(Hobbes)


pgsql-general by date:

Previous
From: Soeren Gerlach
Date:
Subject: Re: Slow dump with pg_dump/pg_restore ? How to improve ?
Next
From: Chris Browne
Date:
Subject: Re: what's best: opteron or xeon for pg 7.4.3?