The following bug has been logged online: Bug reference: 4232 Logged by: Lawrence Cohan Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.5 Operating system: Redhat Linux 4.1.1 Description: CREATE INDEX CONCURRENTLY Details:
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. Exception Type: Npgsql.NpgsqlException Item: NULL Severity: ERROR Code: XX000 BaseMessage: could not open relation with OID 517613 Detail: Hint: Position: Where: SQL statement "SELECT id FROM coupons WHERE merchant_id = $1 AND code = $2 " PL/pgSQL function "set_coupon" line 7 at SQL statement File: heapam.c Line: 700 Routine: relation_open ErrorSql: select * from set_coupon(NULL::int4,91221::int4,'11111'::text,'11111'::text,'1'::int4,NULL ::int4,0::int4,'1'::int4,11::numeric,0::numeric,'2008-06-10'::date,NULL::dat e,TRUE::bool,FALSE::bool) Errors: System.Collections.ArrayList Message: ERROR: XX000: could not open relation with OID 517613 Data: System.Collections.ListDictionaryInternal TargetSite: Void CheckErrors() HelpLink: NULL Source: Npgsql Thanks, Lawrence Cohan. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
