| From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: update before drop causes OID problems in transaction? |
| Date: | 2006-03-18 07:18:10 |
| Message-ID: | Pine.LNX.4.64.0603172316100.11424@discord.dyndns.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Frost | 2006-03-19 02:21:39 | Re: update before drop causes OID problems in transaction? |
| Previous Message | Jeff Frost | 2006-03-18 07:11:33 | Re: update before drop causes OID problems in transaction? |