Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id ED93965014A for ; Fri, 17 Oct 2008 09:10:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 32377-04 for ; Fri, 17 Oct 2008 09:10:22 -0300 (ADT) 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 postgresql.org (Postfix) with ESMTP id 1BFA664FC71 for ; Fri, 17 Oct 2008 09:10:21 -0300 (ADT) 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 m9HCAIVU013973; Fri, 17 Oct 2008 08:10:19 -0400 (EDT) To: "Uwe Bartels" cc: pgsql-admin@postgresql.org Subject: Re: refreshing prepared statements after index rebuild In-reply-to: <8ea917510810170325s769b3cf1k49b94a829d7620a0@mail.gmail.com> References: <8ea917510810170325s769b3cf1k49b94a829d7620a0@mail.gmail.com> Comments: In-reply-to "Uwe Bartels" message dated "Fri, 17 Oct 2008 12:25:37 +0200" Date: Fri, 17 Oct 2008 08:10:18 -0400 Message-ID: <13972.1224245418@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/121 X-Sequence-Number: 30577 "Uwe Bartels" writes: > - just dropping the corrupt index results in errors returned while executing > the existing prepared statements If you were running 8.3 it would Just Work, so I take it you're not. > - restart of the postgres server works of course, but ... you know. that's > the last solution. > - i cannot currently cycle all jdbc connection pools, and bouncing the > app-servers & daemons does heavier damage than cycling the database I'm afraid those are your only options :-( --- pre 8.3, there's no way short of starting fresh sessions to get rid of cached plans for prepared statements. regards, tom lane