pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Frost <jeff@frostconsultingllc.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: update before drop causes OID problems in transaction?
Date: Fri, 17 Mar 2006 23:18:10 -0800 (PST)
Message-ID: <Pine.LNX.4.64.0603172316100.11424@discord.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603172309270.11424@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.0603172309270.11424@discord.dyndns.org>

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



view thread (14+ messages)  latest in thread

Message-ID: <Pine.LNX.4.64.0603172316100.11424@discord.dyndns.org>
Permalink:  ../Pine.LNX.4.64.0603172316100.11424@discord.dyndns.org/
Also on:    postgresql.org/message-id/Pine.LNX.4.64.0603172316100.11424@discord.dyndns.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: jeff@frostconsultingllc.com, tgl@sss.pgh.pa.us
  Subject: Re: update before drop causes OID problems in transaction?
  In-Reply-To: <Pine.LNX.4.64.0603172316100.11424@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.0603172309270.11424@discord.dyndns.org> <Pine.LNX.4.64.0603172316100.11424@discord.dyndns.org>

* 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