Skip site navigation (1) Skip section navigation (2)

Re: refreshing prepared statements after index rebuild

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Uwe Bartels" <uwe(dot)bartels(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: refreshing prepared statements after index rebuild
Date: 2008-10-17 12:10:18
Message-ID: 13972.1224245418@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Uwe Bartels" <uwe(dot)bartels(at)gmail(dot)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

In response to

pgsql-admin by date

Next:From: Isabella GhiureaDate: 2008-10-17 18:24:01
Subject: PostgresSQL DBA books
Previous:From: Uwe BartelsDate: 2008-10-17 10:25:37
Subject: refreshing prepared statements after index rebuild

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group