| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: update before drop causes OID problems in transaction? |
| Date: | 2006-03-20 17:30:43 |
| Message-ID: | 441EE6C3.3050300@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Jeff Frost wrote:
>
>> Another problem might well be with your plpgsql trigger function. If
>> you're dropping/re-creating credit_card_audit then that'll give you
>> the error you're seeing.
>
> The trigger shouldn't be firing at all in this scenario as it is on
> credit_card and not credit_card_audit. Are you saying that it could
> cause this sort of problem even though it doesn't fire?
Actually, my last reply isn't quite accurate. Looking at it, you do
update "credit_card_audit" from within the trigger.
So, it can cause a problem if called, but if it isn't called then it
will not.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-20 22:40:03 | Re: have you feel anything when you read this ? |
| Previous Message | Richard Huxton | 2006-03-20 17:29:03 | Re: update before drop causes OID problems in transaction? |