X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4876C5E46CC for ; Fri, 13 Aug 2004 13:05:47 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 01153-09 for ; Fri, 13 Aug 2004 16:05:45 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by svr1.postgresql.org (Postfix) with ESMTP id 2EB8E5E46CB for ; Fri, 13 Aug 2004 13:05:36 -0300 (ADT) Received: by mproxy.gmail.com with SMTP id 73so17281rnk for ; Fri, 13 Aug 2004 09:05:39 -0700 (PDT) Received: by 10.38.1.79 with SMTP id 79mr46882rna; Fri, 13 Aug 2004 09:05:39 -0700 (PDT) Message-ID: Date: Fri, 13 Aug 2004 11:05:39 -0500 From: Pentilian To: Tom Lane Subject: Re: Wierd Error on update Cc: PostgreSQL Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/132 X-Sequence-Number: 18629 > Original 7.3 release, or (I hope) 7.3.something? 7.3 > > I am getting two errors which are a bit confounding. > > ERROR: pg_class_aclcheck:relation 474653086 not found > > Are there any views involved? No views. Is the statement invoking any functions? The statement is not invoking any fuctions However heres the statements, UPDATE school_info_l SET ind_default_data = 't'; UPDATE school_info_l SET sis_system_id = 9 where school_id IN (492, 434, 436); which are amazingly simple. Both queries return the same exact error, same error. not your > How about triggers? Foreign keys? Rules? Neither of the updates touch any rules. sis_system_id is a foreign key to another table (but the first isnt touching anything that has a trigger or foreign key constraint attached to the column. The table school_info_l has many contraints that affect other tables however > Also, is it always the same number in the error, or does that change > from run to run? The number is the same for each time I run the update file on the same database. with this two queries having the same error. Same result to, if I run these two after the first update file finishes there is no problem, but if I try to run it at the end of hte first file, choke. Very Odd problem to me, since the update statemenets are so simple. -Tom