Received: from megazone23.bigpanda.com ([216.136.151.41]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6JFCVa55069 for ; Thu, 19 Jul 2001 11:12:31 -0400 (EDT) (envelope-from sszabo@megazone23.bigpanda.com) Received: from localhost (sszabo@localhost) by megazone23.bigpanda.com (8.11.2/8.11.2) with ESMTP id f6JFCOj35736; Thu, 19 Jul 2001 08:12:24 -0700 (PDT) Date: Thu, 19 Jul 2001 08:12:24 -0700 (PDT) From: Stephan Szabo To: "David M. Richter" cc: pgsql-sql@postgresql.org Subject: Re: Query optimizing - paradox behave In-Reply-To: <3B56B479.123C88A3@DKFZ-heidelberg.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200107/259 X-Sequence-Number: 4056 What version are you using? (dbPG95GetIndex?) On Thu, 19 Jul 2001, David M. Richter wrote: > Hallo ! > > I want to tune a database. There a many redundant datas in the database > , because of all the relations were consider as n:m relations. But the > most of them are 1:n Relations. So my approach was to cut the > redundancies to get more performance. But .. happens! > > The query with the 3 tables is faster than the query with 2 tables. > > That is paradox to the Explain output. > And: the real database functions like dbPG95GetIndex and all functions > defined by me are slower.