Re: Composite Index question
| От | DM |
|---|---|
| Тема | Re: Composite Index question |
| Дата | |
| Msg-id | AANLkTinTCkryc0L6TfhxH67-ZPkKFeGPNn5Dwminsv1d@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Composite Index question (Rob Sargent <robjsargent@gmail.com>) |
| Ответы |
Re: Composite Index question
|
| Список | pgsql-general |
Its a huge table in production, i dont want to take any risk.
I can simulate and test this but i was to checking to see If any one knows off hand about this.
I can simulate it but
I can simulate and test this but i was to checking to see If any one knows off hand about this.
I can simulate it but
On Wed, Oct 20, 2010 at 4:57 PM, Rob Sargent <robjsargent@gmail.com> wrote:
Hm. Run some queries; drop the second version of the index definition;
re-run the same queries; report to the group. The redundant index isn't
helping, that much is certain.--
On 10/20/2010 05:43 PM, DM wrote:
> Composite Index question:
>
> I have composite index on 3 columns on a table, by mistake the composite
> index was created twice on the table.
>
> Will there any performance issues on this table because of the 2 same
> composite indexes?
>
> Thanks
> Deepak
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: