"Lawrence Cohan" <[EMAIL PROTECTED]> writes:
> We must run maintenance tasks like analyze, reindex and vacuum against our
> PG databases however due to the fact that we are running a 24/7 system that
> requires database access the reindex at the database level is way too heavy
> and it is generating deadlocks. I created a job to CREATE INDEX CONCURRENTLY
> on all user tables and DROP existing INDEX so we donât impact our
> production and now our application is getting errors (like the one below)
> just because the OID for the index was changed. Is there anything we could
> do to workaround this issue as so far the only option that clears it is an
> IIS RESET.
Presumably the errors are coming from re-use of cached plans. The only
really simple solution would be to upgrade to PG 8.3, which knows about
regenerating cached plans when needed.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
