Re: Why isn't it allowed to create an index in a schema other than public?

From: Jorge Godoy <jgodoy(at)gmail(dot)com>
To: Chris Mair <chrisnospam(at)1006(dot)org>
Cc: Jorge Godoy <jgodoy(at)gmail(dot)com>, PostgreSQL General ML <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why isn't it allowed to create an index in a schema other than public?
Date: 2006-11-12 15:38:30
Message-ID: 87d57sekuh.fsf@ieee.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris Mair <chrisnospam(at)1006(dot)org> writes:

> Just say
> create index testing123_index on testing.testing123 (otherthing);
> and you'll otain exactly what you want (see below).
>
> Bye, Chris.

I know I can workaround such debilitation. What I wanted to know is if
there's some reason (such as performance gain, for example) for that
decision.

Using this approach, though, doesn't group all items that belong to a schema
inside of it.

--
Jorge Godoy <jgodoy(at)gmail(dot)com>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-11-12 16:15:49 Re: Why isn't it allowed to create an index in a schema other than public?
Previous Message Joshua D. Drake 2006-11-12 15:33:41 Re: Linux vs. FreeBSD