Received: from zee.computing.com (zee.computing.com [207.8.37.242]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA36644 for ; Fri, 9 Jul 1999 00:25:33 -0400 (EDT) (envelope-from jmr@computing.com) Received: from zee.computing.com (localhost [127.0.0.1]) by zee.computing.com (8.9.3/8.8.5) with ESMTP id XAA12140; Thu, 8 Jul 1999 23:25:04 -0500 (CDT) Message-Id: <199907090425.XAA12140@zee.computing.com> To: jwieck@debis.com (Jan Wieck) cc: ertz@illite.u-strasbg.fr (Olivier Ertz), pgsql-sql@postgreSQL.org Subject: Re: [SQL] RewriteDefine.c : Rule size In-reply-to: Your message of "Thu, 08 Jul 1999 18:30:16 +0200." Date: Thu, 08 Jul 1999 23:25:04 -0500 From: Jim Rowan >> I'm using Postgres 6.4.2. I want to create a view, but a message appear : >> ERROR: DefineQueryRewrite: rule plan string too big. What could be the >> solution to avoid the problem? In fact, I have 31 columns in a table, and >> i want to make a view on this table (with a line restrict = WHERE clause). I get the same error from 6.5 when I create rules that are apparently too complex. My table has 25 or so columns.. >> I watched the RewriteDefine.c code and saw : #define RULE_PLAN_SIZE BLCKSZ >> I thought changing the value of this size, but I don't find the place to >> modify the BLCKSZ value. But, before doing the modification and >> recompile, I would like to have your opinion on the problem...perhaps is >> there an easier way to resolve the problem. wieck> Never did it, but the BLCKSZ is defined in include/config.h. That wieck> is a file generated from config.h.in, so be sure to change it there wieck> and reconfigure before recompiling. Be careful here. We changed BLCKSZ and found some scary results: First we multiplied it * 4. This improved the ability to handle complex rules, but didn't go far enough... (it still wouldn't handle all of what we wanted it to). So we multiplied it * 8. Initdb complained about "float4 not defined". (As I recall.. I'm not where the error message is and thus this may not be 100% accurate...). We quickly changed it back to the original size and are implementing alternative rules... I can understand if it doesn't have enough working space to do what I ask (or whatever the details are behind "rule plan string too big") but if changing BLCKSZ breaks builtin types -- I don't want to mess with it!!!