X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 79C54D1B97B for ; Fri, 5 Sep 2003 21:53:12 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 32171-04 for ; Fri, 5 Sep 2003 18:53:02 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 4B824D1B94F for ; Fri, 5 Sep 2003 18:53:01 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h85LquAn020331; Fri, 5 Sep 2003 17:52:56 -0400 (EDT) To: Neil Conway Cc: Richard Huxton , Bjorn T Johansen , PostgreSQL General , PostgreSQL Performance Subject: Re: [PERFORM] Seq scan of table? In-reply-to: <1062786017.447.1.camel@tokyo> References: <58940.193.212.14.12.1062742087.squirrel@www.havleik.no> <31414.193.212.14.12.1062751674.squirrel@www.havleik.no> <200309051107.12756.dev@archonet.com> <1062786017.447.1.camel@tokyo> Comments: In-reply-to Neil Conway message dated "Fri, 05 Sep 2003 14:20:18 -0400" Date: Fri, 05 Sep 2003 17:52:55 -0400 Message-ID: <20330.1062798775@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/481 X-Sequence-Number: 48703 Neil Conway writes: > On Fri, 2003-09-05 at 06:07, Richard Huxton wrote: >> You should find plenty of discussion of why in the archives, but the short >> reason is that PG's type structure is quite flexible which means it can't >> afford to make too many assumptions. > Well, it's definitely a bug in PG, it's "quite flexible" type structure > notwithstanding. Let's say it's something we'd really like to fix ;-) ... and will, as soon as we can figure out a cure that's not worse than the disease. Dorking around with the semantics of numeric expressions has proven to be a risky business. See, eg, the thread starting here: http://archives.postgresql.org/pgsql-hackers/2002-11/msg00468.php regards, tom lane