Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2P4b8w52117 for ; Sat, 24 Mar 2001 23:37:08 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f2P4auw10342; Sat, 24 Mar 2001 23:36:56 -0500 (EST) To: Mathijs Brands cc: pgsql-sql@postgresql.org Subject: Re: all views in database broken at once In-reply-to: <20010325015704.A46087@ilse.nl> References: <10008.985481400@sss.pgh.pa.us> <20010325015704.A46087@ilse.nl> Comments: In-reply-to Mathijs Brands message dated "Sun, 25 Mar 2001 01:57:04 +0100" Date: Sat, 24 Mar 2001 23:36:56 -0500 Message-ID: <10339.985495016@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/486 X-Sequence-Number: 2157 Mathijs Brands writes: > How about being able to recompile them (keeping the SQL around in the > system catalogs)? Doesn't Oracle allow you to do something like that? That's another possibility. It's not real clear that there's any advantage to storing rules in preparsed form to begin with --- if we just stored the original text and reparsed it each time it was read, the system would be vastly more flexible, and probably not noticeably slower. Right now the parser doesn't really support this: there's no way to extract the portion of the original query string that corresponds to the body of the CREATE RULE/VIEW command. But that could be fixed with some straightforward hacking... regards, tom lane