Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 2CAEB1337BC9 for ; Thu, 16 Dec 2010 12:28:09 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 19127-01-3 for ; Thu, 16 Dec 2010 16:28:02 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 7B6441337BC8 for ; Thu, 16 Dec 2010 12:27:56 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id oBGGRskD022395; Thu, 16 Dec 2010 11:27:54 -0500 (EST) To: Eric Comeau cc: pgsql-performance@postgresql.org Subject: Re: How to get FK to use new index without restarting the database In-reply-to: References: Comments: In-reply-to Eric Comeau message dated "Thu, 16 Dec 2010 07:12:03 -0500" Date: Thu, 16 Dec 2010 11:27:54 -0500 Message-ID: <22394.1292516874@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201012/199 X-Sequence-Number: 41651 Eric Comeau 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