<div dir="ltr"><div class="gmail_quote">On Tue, Jul 10, 2012 at 11:11 AM, Greg Stark <span dir="ltr"><<a
href="mailto:stark@mit.edu"target="_blank">stark@mit.edu</a>></span> wrote:<br /><blockquote class="gmail_quote"
style="margin:00 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Jul 10, 2012 at 3:44 PM,
TomLane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>> wrote:<br /> >> The problem you describe
isone of constraints and dependencies and<br /> >> not one of indexes. It seems what you really want is a way to
alter<br/> >> foreign key dependencies to depend on a new index. Either an explicit<br /> >> command that
letsyou set the new dependency or what seems even better<br /> >> would be to have DROP INDEX check any dependent
objectsto see if<br /> >> there's another index that can satisfy them and change their<br /> >>
dependency.<br/> ><br /> > Either of these have exactly the same issue, namely their correctness<br /> >
dependson determining if two indexes have identical properties.<br /><br /></div>This doesn't sound right to me. In
thesecases all it would have to<br /> know about is the same set of properties that CREATE CONSTRAINT looks<br /> for
tofind a satisfactory index to depend on.<br /><span class="HOEnZb"><font
color="#888888"></font></span></blockquote></div><brclear="all" />I like the DROP index idea, but the silent
side-effectmay not make people happy. Can you give me a pointer to relevant code.<br /><br />-- <br /><div
dir="ltr">GurjeetSingh<br />EnterpriseDB Corporation<br />The Enterprise PostgreSQL Company<br /></div><br /></div>