Re: update before drop causes OID problems in transaction? - Mailing list pgsql-sql

From Jeff Frost
Subject Re: update before drop causes OID problems in transaction?
Date
Msg-id Pine.LNX.4.64.0603172316100.11424@discord.dyndns.org
Whole thread Raw
In response to Re: update before drop causes OID problems in transaction?  (Jeff Frost <jeff@frostconsultingllc.com>)
List pgsql-sql
On Fri, 17 Mar 2006, Jeff Frost wrote:

> I'll try that and see if that makes the difference, since we're recreating 
> (create or replace) that function in that transaction anyway, but perhaps 
> that needs to happen before the update.

I added this at the top of the transaction:

DROP FUNCTION public.audit_credit_card ();
and had to move the drop trigger above it, so the order looked like so:

BEGIN;
DROP RULE credit_card_audit_no_update ON credit_card_audit;
DROP TRIGGER audit_credit_card ON credit_card;
DROP FUNCTION public.audit_credit_card ();

Same result:

psql:transaction-test-case.sql:212: ERROR:  could not open relation with OID 
29976142



-- 
Jeff Frost, Owner     <jeff@frostconsultingllc.com>
Frost Consulting, LLC     http://www.frostconsultingllc.com/
Phone: 650-780-7908    FAX: 650-649-1954


pgsql-sql by date:

Previous
From: Jeff Frost
Date:
Subject: Re: update before drop causes OID problems in transaction?
Next
From: Андрей Долин
Date:
Subject: how to get current recursion level in recursive trigger?