X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 613BB9DCC0E for ; Fri, 17 Mar 2006 18:52:51 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 33113-08 for ; Fri, 17 Mar 2006 18:52:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2B90B9DCC0F for ; Fri, 17 Mar 2006 18:52:48 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k2HMqnGR010755; Fri, 17 Mar 2006 17:52:49 -0500 (EST) To: Jeff Frost cc: pgsql-sql@postgresql.org Subject: Re: update before drop causes OID problems in transaction? In-reply-to: References: Comments: In-reply-to Jeff Frost message dated "Fri, 17 Mar 2006 14:41:58 -0800" Date: Fri, 17 Mar 2006 17:52:49 -0500 Message-ID: <10754.1142635969@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.113 required=5 tests=[AWL=0.113] X-Spam-Score: 0.113 X-Spam-Level: X-Archive-Number: 200603/257 X-Sequence-Number: 24603 Jeff Frost writes: > After commit, I get a lovely: > ERROR: could not open relation with OID x Could we see a complete test case, rather than handwaving? I'd expect some issues like this if you were using any prepared statements or plpgsql functions with non-EXECUTEd queries involving the dropped table, but your description doesn't mention either of those risk factors. regards, tom lane