DM <dm.aeqa@xxxxxxxxx> writes: > I know there is no benfit of having duplicate indexes. > Inorder for me to make change on production it requires lot of approvals and > stuff. > I wnat to know if there is any major performance drawback for having > duplicate composite index, Of course there is: it doubles the index-update overhead every time you update the table, in return for no benefit whatsoever. Get rid of the duplicate index. (Now, if the table is seldom updated, it might not be urgent to do so. But you ought to plan on doing it.) regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
