From: Tom Lane <tgl@sss.pgh.pa.us>
To: Uwe Bartels <uwe.bartels@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: refreshing prepared statements after index rebuild
Date: Fri, 17 Oct 2008 08:10:18 -0400
Message-ID: <13972.1224245418@sss.pgh.pa.us> (raw)
In-Reply-To: <8ea917510810170325s769b3cf1k49b94a829d7620a0@mail.gmail.com>
References: <8ea917510810170325s769b3cf1k49b94a829d7620a0@mail.gmail.com>
"Uwe Bartels" <uwe.bartels@gmail.com> 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
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, uwe.bartels@gmail.com
Subject: Re: refreshing prepared statements after index rebuild
In-Reply-To: <13972.1224245418@sss.pgh.pa.us>
* 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