| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Lawrence Cohan" <lawrencec(at)1shoppingcart(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4232: CREATE INDEX CONCURRENTLY |
| Date: | 2008-06-10 20:58:23 |
| Message-ID: | 24522.1213131503@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Lawrence Cohan" <lawrencec(at)1shoppingcart(dot)com> 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 dont 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lawrence Cohan | 2008-06-10 21:11:25 | Re: BUG #4232: CREATE INDEX CONCURRENTLY |
| Previous Message | Lawrence Cohan | 2008-06-10 18:44:31 | BUG #4232: CREATE INDEX CONCURRENTLY |