Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 3FCD64772A6 for ; Fri, 17 Jan 2003 10:11:30 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id D6555477264 for ; Fri, 17 Jan 2003 10:11:19 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0HFBH5u011881; Fri, 17 Jan 2003 10:11:19 -0500 (EST) To: Jeff Cc: Roman Fail , Josh Berkus , "sszabo@megazone23.bigpanda.com" , "pgsql-performance@postgresql.org" Subject: Re: 7.3.1 New install, large queries are slow In-reply-to: References: Comments: In-reply-to Jeff message dated "Fri, 17 Jan 2003 09:00:19 -0500" Date: Fri, 17 Jan 2003 10:11:17 -0500 Message-ID: <11880.1042816277@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/180 X-Sequence-Number: 827 Jeff writes: > Perhaps this should go on the TODO - when one side is an int8 and the > other is a literal number assume the number to be int8 instead of int4? It's been on TODO for so long that it's buried near the bottom. * Allow SELECT * FROM tab WHERE int2col = 4 to use int2col index, int8, float4, numeric/decimal too [optimizer] This behavior interacts with enough other stuff that we can't just change it willy-nilly. See many past discussions in the pghackers archives if you want details. A recent example of a promising-looking fix crashing and burning is http://fts.postgresql.org/db/mw/msg.html?mid=1357121 regards, tom lane