Re: Composite Index question - Mailing list pgsql-general

From DM
Subject Re: Composite Index question
Date
Msg-id AANLkTinTCkryc0L6TfhxH67-ZPkKFeGPNn5Dwminsv1d@mail.gmail.com
Whole thread Raw
In response to Re: Composite Index question  (Rob Sargent <robjsargent@gmail.com>)
Responses Re: Composite Index question  (Rob Sargent <robjsargent@gmail.com>)
List 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
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 by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Composite Index question
Next
From: Gabi Julien
Date:
Subject: Custom cache implemented in a postgresql C function