From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Jorge Godoy <jgodoy(at)gmail(dot)com> |
Cc: | Chris Mair <chrisnospam(at)1006(dot)org>, 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 16:15:49 |
Message-ID: | 20061112161549.GB1586@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Nov 12, 2006 at 01:38:30PM -0200, Jorge Godoy wrote:
> 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.
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.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Mair | 2006-11-12 16:26:42 | Re: Why isn't it allowed to create an index in a schema |
Previous Message | Jorge Godoy | 2006-11-12 15:38:30 | Re: Why isn't it allowed to create an index in a schema other than public? |