Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA59193 for ; Thu, 21 Oct 1999 09:31:48 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA16444; Thu, 21 Oct 1999 09:30:43 -0400 (EDT) To: Nik Putnam cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] bad select performance fixed by forbidding hash joins In-reply-to: Your message of Thu, 21 Oct 1999 00:22:13 -0700 <380EBF24.3CCDBC1B@spinon.berkeley.edu> Date: Thu, 21 Oct 1999 09:30:43 -0400 Message-ID: <16442.940512643@sss.pgh.pa.us> From: Tom Lane Nik Putnam writes: > I tried this out to see if it would speed up *my* query too. > The query went much faster, but gave different results! > [nputnam@spinon ~]$ setenv PGOPTIONS "-fh" > [nputnam@spinon ~]$ psql -e expression < query.sql > gives 15 rows of output in 1s. > [nputnam@spinon ~]$ unsetenv PGOPTIONS > [nputnam@spinon ~]$ psql -e expression < query.sql > gives 289 rows of output in 51s > The slow one is giving the right answer. > Why might they be different? That would be a bug, without question. Can you provide a repeatable test case? regards, tom lane