Received: from thor.tht.net (thor.tht.net [209.47.145.4]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA5I9Ds37838 for ; Sun, 5 Nov 2000 13:09:13 -0500 (EST) (envelope-from depesz@gruby.cs.net.pl) Received: from gruby_int.cs.net.pl (cafe1.rem.pl [195.205.133.61]) by thor.tht.net (8.9.3/8.9.3) with ESMTP id JAA27201 for ; Sun, 5 Nov 2000 09:07:47 GMT (envelope-from depesz@gruby.cs.net.pl) Received: (from localhost user: 'depesz' uid#500 fake: STDIN (depesz@gruby.cs.net.pl)) by gruby.cs.net.pl id ; Sun, 5 Nov 2000 12:50:03 +0100 Date: Sun, 5 Nov 2000 12:50:03 +0100 From: hubert depesz lubaczewski To: pgSQL Subject: Time penalty on VIEWS on VIEWS Message-ID: <20001105125003.D27532@gruby> Reply-To: depesz@depesz.pl Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i X-Archive-Number: 200011/33 X-Sequence-Number: 64 Hi, My situation: VIEW A is grouping information from 2 tables (B,C). I have to make another VIEW with additional WHERE statement compared in VIEW A. I can make this as a VIEW groupping tables B and C, or makeing VIEW of VIEW A. I know that second sollution is more flexible but there should be some kind of time penalty. I'm wondering how much it is. regards, depesz -- hubert depesz lubaczewski ------------------------------------------------------------------------ najwspanialszą rzeczą jaką dało nam nowoczesne społeczeństwo, jest niesamowita wręcz łatwość unikania kontaktów z nim ...