Re: Re: Allow replacement of bloated primary key indexes without foreign key rebuilds - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Re: Allow replacement of bloated primary key indexes without foreign key rebuilds
Date
Msg-id CAM-w4HNevJ6HkMW3UBSRnm_DjMPuBzXwWZQzWqnN3SerMZeVhA@mail.gmail.com
Whole thread Raw
In response to Re: Re: Allow replacement of bloated primary key indexes without foreign key rebuilds  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: Allow replacement of bloated primary key indexes without foreign key rebuilds  (Gurjeet Singh <singh.gurjeet@gmail.com>)
List pgsql-hackers
On Tue, Jul 10, 2012 at 3:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> The problem you describe is one of constraints and dependencies and
>> not one of indexes. It seems what you really want is a way to alter
>> foreign key dependencies to depend on a new index. Either an explicit
>> command that lets you set the new dependency or what seems even better
>> would be to have DROP INDEX check any dependent objects to see if
>> there's another index that can satisfy them and change their
>> dependency.
>
> Either of these have exactly the same issue, namely their correctness
> depends on determining if two indexes have identical properties.

This doesn't sound right to me. In these cases all it would have to
know about is the same set of properties that CREATE CONSTRAINT looks
for to find a satisfactory index to depend on.

-- 
greg


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: expression evaluation with expected datatypes
Next
From: Shaun Thomas
Date:
Subject: Re: Synchronous Standalone Master Redoux