From: Eric Comeau <ecomeau@signiant.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to get FK to use new index without restarting the database
Date: Fri, 17 Dec 2010 01:53:56 -0500
Message-ID: <ief1e3$4ac$1@news.hub.org> (raw)
In-Reply-To: <22394.1292516874@sss.pgh.pa.us>
References: <iecvmj$1j93$1@news.hub.org>
<22394.1292516874@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ecomeau@signiant.com
Subject: Re: How to get FK to use new index without restarting the database
In-Reply-To: <ief1e3$4ac$1@news.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox