Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e7MIGtT66446 for ; Tue, 22 Aug 2000 14:16:55 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id OAA13723; Tue, 22 Aug 2000 14:16:20 -0400 (EDT) To: Jan Wieck cc: Stephan Szabo , Joerg Hessdoerfer , pgsql-sql@postgresql.org Subject: Re: Continuous inserts... In-reply-to: <200008221831.NAA01610@jupiter.greatbridge.com> References: <200008221831.NAA01610@jupiter.greatbridge.com> Comments: In-reply-to Jan Wieck message dated "Tue, 22 Aug 2000 13:31:31 -0500" Date: Tue, 22 Aug 2000 14:16:20 -0400 Message-ID: <13720.966968180@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200008/233 Jan Wieck writes: > I haven't looked at the code, but pg_class only has a boolean > telling if a class has rules or not. Could it be that adding > more rules (or dropping just a few instead of all) doesn't > update the pg_class tuple, thus the syscache for the table > isn't invalidated and other backends continue to use the old > information instead of rescanning pg_rewrite? This is done correctly in current sources --- see setRelhasrulesInRelation(). However I recall having dorked with that code not long ago, and I forget what it looked like before. Perhaps 7.0.* is broken in this respect? Would think people would have noticed, though. regards, tom lane