pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Richard Huxton <dev@archonet.com>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: update before drop causes OID problems in transaction?
Date: Mon, 20 Mar 2006 17:30:43 +0000
Message-ID: <441EE6C3.3050300@archonet.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603200910200.30710@discord.dyndns.org>
References: <Pine.LNX.4.64.0603171434230.11424@discord.dyndns.org>
	<10754.1142635969@sss.pgh.pa.us>
	<Pine.LNX.4.64.0603171454170.11424@discord.dyndns.org>
	<Pine.LNX.4.64.0603172012190.11424@discord.dyndns.org>
	<13574.1142663266@sss.pgh.pa.us>
	<Pine.LNX.4.64.0603172233140.11424@discord.dyndns.org>
	<13832.1142664905@sss.pgh.pa.us>
	<Pine.LNX.4.64.0603181802170.11424@discord.dyndns.org>
	<441EB977.3000706@archonet.com>
	<Pine.LNX.4.64.0603200910200.30710@discord.dyndns.org>

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



view thread (14+ messages)

Message-ID: <441EE6C3.3050300@archonet.com>
Permalink:  ../441EE6C3.3050300@archonet.com/
Also on:    postgresql.org/message-id/441EE6C3.3050300@archonet.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: dev@archonet.com, jeff@frostconsultingllc.com, tgl@sss.pgh.pa.us
  Subject: Re: update before drop causes OID problems in transaction?
  In-Reply-To: <441EE6C3.3050300@archonet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox