Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e6LHkJh77306 for ; Fri, 21 Jul 2000 13:46:19 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id NAA17228; Fri, 21 Jul 2000 13:46:12 -0400 (EDT) To: "Mitch Vincent" cc: pgsql-sql@postgresql.org Subject: Re: Timestamp indexes In-reply-to: <004901bff33a$bd41ebd0$4100000a@doot> References: <001d01bff323$39cdb250$4100000a@doot> <13354.964192504@sss.pgh.pa.us> <007701bff32b$ce21d410$4100000a@doot> <13585.964200369@sss.pgh.pa.us> <004901bff33a$bd41ebd0$4100000a@doot> Comments: In-reply-to "Mitch Vincent" message dated "Fri, 21 Jul 2000 13:40:19 -0400" Date: Fri, 21 Jul 2000 13:46:12 -0400 Message-ID: <17224.964201572@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/215 "Mitch Vincent" writes: > Looks like that index scan is very unattractive... Yes, though not as bad as the cost estimator thinks (almost a 5:1 ratio in estimated cost, but hardly any difference in real runtime). Still have some work to do in tweaking the estimates, obviously. regards, tom lane