X-Original-To: pgsql-sql@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id C290247592C for ; Mon, 10 Mar 2003 23:54:34 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2B4sTub002668; Mon, 10 Mar 2003 23:54:29 -0500 (EST) To: Josh Berkus Cc: "A.M." , pgsql-sql@postgresql.org Subject: Re: explain (internal feature) In-reply-to: <200303102008.56022.josh@agliodbs.com> References: <185A05F6-5371-11D7-98AA-0030657192DA@cmu.edu> <200303102008.56022.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Mon, 10 Mar 2003 20:08:56 -0800" Date: Mon, 10 Mar 2003 23:54:29 -0500 Message-ID: <2667.1047358469@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/254 X-Sequence-Number: 12294 Josh Berkus writes: >> db=#explain vacuum; >> to return: >> NOTICE: "vacuum" is an internal postgresql feature. >> instead of: >> ERROR: parser: parse error at or near "vacuum" at character 9 > No, it would not. Actually, it's a fair question considering that the 7.3 man page for EXPLAIN says you can explain "any query". But CVS-tip documentation says that EXPLAIN can explain Any SELECT, INSERT, UPDATE, DELETE, EXECUTE, or DECLARE CURSOR query. which I think is sufficient description. I'm not really eager to enlarge the parser enough to accept EXPLAIN when it's only gonna fail anyway... regards, tom lane