Received: from sysadmin.chi.wdr.com (sysadmin.chi.ubswarburg.com [146.180.1.66]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7E5VXP44953 for ; Tue, 14 Aug 2001 01:31:33 -0400 (EDT) (envelope-from devin@sysadmin.chi.wdr.com) Received: from devin by sysadmin.chi.wdr.com with local (Exim 3.12 #2) id 15WWnG-000600-00; Tue, 14 Aug 2001 00:31:10 -0500 Date: Tue, 14 Aug 2001 00:31:04 -0500 (CDT) From: Tod McQuillin X-X-Sender: To: Josh Berkus cc: Tom Lane , Subject: Re: Eh? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200108/174 X-Sequence-Number: 4396 On Mon, 13 Aug 2001, Josh Berkus wrote: > > > SHould I be concerned about this? > > > > > DEBUG: geqo_main: using edge recombination crossover [ERX] > > > > Nope. See > > http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/geqo.html > > Cool! I love it when I actually get the chance to see some advance > theory applied. And congrats on implementing it! Yeah, this is really excellent. > Of course, we'll see if it really boosts query optimization when there's > a full data population. This view has 3 UNION statements, 11 > subselects, 35 JOINS, and calls on 3 custom formatting functions ... This makes me wonder... in the case of a stored complex view, would it be helpful to ask PostgreSQL to spend extra time in query optimisation and then cache the result? Or does it do this already? -- Tod McQuillin