Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I don't see how this is a showstopper. At creation time we may decree
> that the database is "incomplete", and users can't normally connect to
> it; we only allow that after a phase of correcting minor issues, such as
> reindexing if necessary. I recal
On Mon, Mar 28, 2005 at 10:54:16AM -0500, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Maybe it would work if we forced indexes on shared relations to be
> > scanned using a fixed collation.
>
> The shared relations only have indexes on name, oid, and integer:
> select distinct
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Maybe it would work if we forced indexes on shared relations to be
scanned using a fixed collation.
The shared relations only have indexes on name, oid, and integer:
select distinct atttypid::regtype
from pg_class c join pg_attribute a on c.oid = a.attreli
On Mon, Mar 28, 2005 at 12:16:42PM +0400, Alexey Slynko wrote:
> this patch allow to use database locale settings. It remove cluster locale
> settings, and append LCCTYPE and
> LCCOLLATE items to CREATE DATABASE syntax.
>
> Any considerations ?
The problem with this is what happens to indexes o
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Maybe it would work if we forced indexes on shared relations to be
> scanned using a fixed collation.
The shared relations only have indexes on name, oid, and integer:
select distinct atttypid::regtype
from pg_class c join pg_attribute a on c.oid = a.at
On Mon, Mar 28, 2005 at 12:16:42PM +0400, Alexey Slynko wrote:
> this patch allow to use database locale settings. It remove cluster locale
> settings, and append LCCTYPE and
> LCCOLLATE items to CREATE DATABASE syntax.
>
> Any considerations ?
The problem with this is what happens to indexes
