Message-ID: <3E2EC4E9.7000809@klaster.net>
Date: Wed, 22 Jan 2003 17:20:57 +0100
From: Tomasz Myrta <jasiek@klaster.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US;
	rv:1.2b) Gecko/20021016
MIME-Version: 1.0
To: Jan Wieck <JanWieck@Yahoo.com>
Cc: Ries van Twisk <ries@jongert.nl>, pgsql-sql@postgresql.org
Subject: Re: To use a VIEW or not to use a View.....
References: <002001c2c228$bc3d2780$f100000a@IT001>
	<3E2EBCEE.EF487ECC@Yahoo.com>
In-Reply-To: <002001c2c228$bc3d2780$f100000a@IT001>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Jan Wieck wrote:

>Use tables, views and views over views, it's all fine and your indexes
>will be used.

I can't agree with using views over views. It has some limitations.
I asked about it on this list several months ago
and Tom Lane's conclusion was:


>> Tomasz Myrta <jasiek@klaster.net> writes:
>> I'd like to split queries into views, but I can't join them - planner 
>> search all of records instead of using index. It works very slow.


I think this is the same issue that Stephan identified in his response
to your other posting ("sub-select with aggregate").  When you write
	FROM x join y using (col) WHERE x.col = const
the WHERE-restriction is only applied to x.  I'm afraid you'll need
to write
	FROM x join y using (col) WHERE x.col = const AND y.col = const
Ideally you should be able to write just
	FROM x join y using (col) WHERE col = const
but I think that will be taken the same as "x.col = const" :-(

			regards, tom lane


I don't know if anything changed on 7.3.

Regards,
Tomasz Myrta