Skip site navigation (1) Skip section navigation (2)

Re: Internationalization

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Dennis Gearon <gearond(at)fireserve(dot)net>
Cc: pgsql General List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Internationalization
Date: 2004-06-30 22:10:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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]>)
"The problem with the future is that it keeps turning into the present"

In response to

pgsql-general by date

Next:From: wespvpDate: 2004-06-30 23:23:08
Subject: Re: backups
Previous:From: Soeren GerlachDate: 2004-06-30 22:08:46
Subject: Re: Slow dump with pg_dump/pg_restore ? How to improve ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group