From: Eric Comeau <ecomeau@signiant.com>
Subject: Re: How to get FK to use new index without restarting the
 database
Date: Fri, 17 Dec 2010 01:53:56 -0500
Organization: Hub.Org Networking Services
Lines: 21
Message-ID: <ief1e3$4ac$1@news.hub.org>
References: <iecvmj$1j93$1@news.hub.org> <22394.1292516874@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: <22394.1292516874@sss.pgh.pa.us>
To: pgsql-performance@postgresql.org

On 10-12-16 11:27 AM, Tom Lane wrote:
> Eric Comeau<ecomeau@signiant.com>  writes:
>> Is there a way force the db to re-evaluate its execution plan for a FK
>> without bouncing the DB?
>
>>    PostgreSQL 8.1.17
>
> You don't need to bounce the whole DB, but you will need to start fresh
> sessions.  We didn't add automatic invalidation of those plans until 8.3.
>
> 			regards, tom lane
>

We confirmed that disconnecting and reconnecting resolves the issue.

Thanks to all that helped.

I replied to Tom and the list yesterday from my e-mail, but I don't see 
my reply here, so it must be stuck in the ether somewhere....

Eric