X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6838A9DCB6A for ; Thu, 16 Feb 2006 12:13:02 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 26393-07 for ; Thu, 16 Feb 2006 12:13:00 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 22DAA9DCABF for ; Thu, 16 Feb 2006 12:12:59 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k1GGCoCh028734; Thu, 16 Feb 2006 11:12:50 -0500 (EST) To: Jerry Sievers cc: pgsql-admin@postgresql.org Subject: Re: Dropping of indexes with cached PL query plans In-reply-to: References: Comments: In-reply-to Jerry Sievers message dated "16 Feb 2006 10:36:01 -0500" Date: Thu, 16 Feb 2006 11:12:50 -0500 Message-ID: <28733.1140106370@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.11 required=5 tests=[AWL=0.110] X-Spam-Score: 0.11 X-Spam-Level: X-Archive-Number: 200602/196 X-Sequence-Number: 20617 Jerry Sievers writes: > Any of these connections that may have previously executed PL > functions which planned an index lookup are now going to fault if same > index goes away. > Had wondered if a postmaster 'reload' would elicit a recompiling of > func query plans (did *not* see this in the docs but was hopeful...). Starting a fresh session (database connection) is sufficient, you need not bounce the postmaster as such. We are looking at making replanning happen automatically after a schema change; I'm hopeful that that gets done for 8.2. regards, tom lane