Received: from bjke.com (firewall-user@ganymede.bjke.com [144.210.8.38]) by hub.org (8.9.1/8.9.1) with ESMTP id MAA07968 for ; Wed, 28 Oct 1998 12:10:39 -0500 (EST) (envelope-from djackson@cpsgroup.com) Received: by bjke.com; id LAA20241; Wed, 28 Oct 1998 11:10:35 -0600 (CST) Received: from cpsmail.cpsgroup.com(144.210.12.11) by gauntlet.bjke.com via smap (4.1) id xmad19385; Wed, 28 Oct 98 11:09:43 -0600 Received: by cpsmail with Internet Mail Service (5.0.1458.49) id <4KHRKGCM>; Wed, 28 Oct 1998 11:11:55 -0600 Message-ID: From: "Jackson, DeJuan" To: jwieck@debis.com, caffeine@toodarkpark.org Cc: selkovjr@mcs.anl.gov, pierre@desertmoon.com, pgsql-sql@postgreSQL.org Subject: RE: [SQL] Joining bug???? Date: Wed, 28 Oct 1998 11:11:51 -0600 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain > > try making a view. from what others have said, views save the query > plan > > and have usually, at least for me, been _alot_ faster than normal > queries. > > Views don't save query plans. They are parsetree templates in > query rewrite rules. > So, could you explain what counts for the speed increase. Is the parse stage really that costly? -DEJ