From: Uwe Bartels <uwe.bartels@gmail.com>
To: pgsql-admin@postgresql.org
Subject: refreshing prepared statements after index rebuild
Date: Fri, 17 Oct 2008 12:25:37 +0200
Message-ID: <8ea917510810170325s769b3cf1k49b94a829d7620a0@mail.gmail.com> (raw)
Hi,
we have a corrupt index (size=20GB) and are about to create a new index
parallel to the corrupted index.
the index is running on a heavyly used online database with oltp character.
The question is what's the softest way to switch to the new index. there are
several application servers, webapplications and other daemons which use
prepared statements on the table associated with that index.
- just dropping the corrupt index results in errors returned while executing
the existing prepared statements
- 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
Is there a way to centrally refresh the existing prepared statements?
any hint that results in a soft switch without disturbance of the
application is appreciated.
best regards,
Uwe
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: uwe.bartels@gmail.com
Subject: Re: refreshing prepared statements after index rebuild
In-Reply-To: <8ea917510810170325s769b3cf1k49b94a829d7620a0@mail.gmail.com>
* 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