I'm a little confused about what you mean when you say you can't specify where the index should go. Schemas are a logical division, not a physical one. There's no logical reason to have the index for a table in a separate schema. (And if one were limiting which schemas a user could access, there
Tom Lane <[EMAIL PROTECTED]> writes:
> Jorge Godoy <[EMAIL PROTECTED]> writes:
>> I'd like to know if there's any reasoning for not allowing creating an index
>> inside the same schema where the table is.
>
> Actually, you've got that exactly backwards: it's not allowed to have
> the index in a *d
Martijn van Oosterhout writes:
> I think his point was that the index is always in the same schema as
> the table itself. It states this quite clearly in the documentation. So
> what exactly is the debilitation? It seems to be doing exactly what you
> want.
As Homer Simpson says: D'oh! :-)
I've
Jorge Godoy <[EMAIL PROTECTED]> writes:
> I'd like to know if there's any reasoning for not allowing creating an index
> inside the same schema where the table is.
Actually, you've got that exactly backwards: it's not allowed to have
the index in a *different* schema from its parent table. Hence
> > 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
On Sun, Nov 12, 2006 at 01:38:30PM -0200, Jorge Godoy wrote:
> Chris Mair <[EMAIL PROTECTED]> 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 s
Chris Mair <[EMAIL PROTECTED]> 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 per
> I'd like to know if there's any reasoning for not allowing creating an index
> inside the same schema where the table is. For example, if I have a
> multi-company database where each company has its own schema and its employees
> table, shouldn't I have a different index for each of those? What
Hi!
I'd like to know if there's any reasoning for not allowing creating an index
inside the same schema where the table is. For example, if I have a
multi-company database where each company has its own schema and its employees
table, shouldn't I have a different index for each of those? What
