"Uwe Bartels" <[EMAIL PROTECTED]> 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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
