| From: | "Michael Nolan" <htfoot(at)gmail(dot)com> |
|---|---|
| To: | "Jorge Godoy" <godoy(at)ieee(dot)org> |
| Cc: | "Jorge Godoy" <jgodoy(at)gmail(dot)com>, "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-13 01:35:54 |
| Message-ID: | 4abad0eb0611121735o5a8aa186if6a518b87d5f2fe0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
are good reasons NOT to have the index in a separate schema.)
If, on the other hand, you want to control where the index is physically
stored, for example to optimized disk access times, you should use
tablespaces.
--
Mike Nolan
On 11/12/06, Jorge Godoy <godoy(at)ieee(dot)org> wrote:
>
>
> I've seen it now... I just can't specify where the index should go, it
> always
> goes with the table... That's fine...
>
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2006-11-13 09:02:47 | Re: Why overlaps is not working |
| Previous Message | novnov | 2006-11-12 22:21:10 | Re: Table and Field namestyle best practices? |