Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 398D247644B for ; Wed, 22 Jan 2003 10:36:01 -0500 (EST) Received: from wolff.to (wolff.to [66.93.249.74]) by postgresql.org (Postfix) with SMTP id 3D6DD476023 for ; Wed, 22 Jan 2003 10:35:35 -0500 (EST) Received: (qmail 5510 invoked by uid 500); 22 Jan 2003 15:48:10 -0000 Date: Wed, 22 Jan 2003 09:48:10 -0600 From: Bruno Wolff III To: Ries van Twisk Cc: pgsql-sql@postgresql.org Subject: Re: To use a VIEW or not to use a View..... Message-ID: <20030122154810.GA5475@wolff.to> Mail-Followup-To: Ries van Twisk , pgsql-sql@postgresql.org References: <002001c2c228$bc3d2780$f100000a@IT001> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002001c2c228$bc3d2780$f100000a@IT001> User-Agent: Mutt/1.3.25i X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/335 X-Sequence-Number: 11200 On Wed, Jan 22, 2003 at 16:12:52 +0100, Ries van Twisk wrote: > Dear PostgreSQL users, > > I understand that when a frontend accesses a VIEW that PostgreSQL cannot use > a index on that view. > For example when I do this: SELECT * FROM full_cablelist WHERE > projectocode=5; Correct? For the most part views work like macros for selects and indexes should be usable. You can test this yourself using EXPLAIN to compare plans both using and not using a view on a table.