From: Eric Comeau <ecomeau@signiant.com>
Subject: Re: How to get FK to use new index without restarting the
 database
Date: Thu, 16 Dec 2010 07:55:46 -0500
Organization: Hub.Org Networking Services
Lines: 46
Message-ID: <4D0A0C52.10001@signiant.com>
References: <iecvmj$1j93$1@news.hub.org>
	<OFC47B4729.FAF27BE5-ON652577FB.0044D994-652577FB.00452962@ibsplc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
To: Jayadevan M <Jayadevan.Maymala@ibsplc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
In-Reply-To: 
 <OFC47B4729.FAF27BE5-ON652577FB.0044D994-652577FB.00452962@ibsplc.com>
To: pgsql-performance@postgresql.org

On 10-12-16 07:34 AM, Jayadevan M wrote:
> Hello,
>> Is there a way force the db to re-evaluate its execution plan for a FK
>> without bouncing the DB?
>>
>>    PostgreSQL 8.1.17
>>
>> In our latest release our developers have implemented some new foreign
>> keys but forgot to create indexes on these keys.
>>
>> The problem surfaced at one of our client installs where a maintenance
>> DELETE query was running for over 24 hrs. We have since then identified
>> the missing indexes and have sent the client a script to create them,
>> but in our testing we could not been able to get postgres to use the new
>
>> index for the FK cascade delete without bouncing the database.
> Did you try analyze? May be it will help.
> http://www.postgresql.org/docs/9.0/static/sql-analyze.html

Yes we did. Thanks for the suggestion.

>
> Regards,
> Jayadevan
>
>
>
>
>
> DISCLAIMER:
>
> "The information in this e-mail and any attachment is intended only for
> the person to whom it is addressed and may contain confidential and/or
> privileged material. If you have received this e-mail in error, kindly
> contact the sender and destroy all copies of the original communication.
> IBS makes no warranty, express or implied, nor guarantees the accuracy,
> adequacy or completeness of the information contained in this email or any
> attachment and is not liable for any errors, defects, omissions, viruses
> or for resultant loss or damage, if any, direct or indirect."
>
>
>
>
>
>