X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E8F17D1B4A2 for ; Mon, 5 Jan 2004 15:23:31 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 95119-02 for ; Mon, 5 Jan 2004 11:22:45 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 79814D1B4AD for ; Mon, 5 Jan 2004 11:22:36 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i05FMW19009967; Mon, 5 Jan 2004 10:22:32 -0500 (EST) To: David Teran Cc: Shridhar Daithankar , pgsql-performance@postgresql.org Subject: Re: optimizing Postgres queries In-reply-to: <3796212E-3F79-11D8-A528-000A95A6F0DC@cluster9.com> References: <4B0023AC-3F72-11D8-B3EB-000A95A6F0DC@cluster9.com> <200401051705.55120.shridhar_daithankar@myrealbox.com> <64C8DBBA-3F77-11D8-A528-000A95A6F0DC@cluster9.com> <200401051740.05006.shridhar_daithankar@myrealbox.com> <3796212E-3F79-11D8-A528-000A95A6F0DC@cluster9.com> Comments: In-reply-to David Teran message dated "Mon, 05 Jan 2004 13:18:06 +0100" Date: Mon, 05 Jan 2004 10:22:32 -0500 Message-ID: <9966.1073316152@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/33 X-Sequence-Number: 5208 David Teran writes: > This is my bigger problem: i am using EOF (OR mapping tool) which frees > me more or less form writing a lot of SQL. If i need to typecast to use > an index then i have to see how to do this with this framework. It's worth pointing out that this problem is fixed (at long last) in CVS tip. Ypu probably shouldn't expend large amounts of effort on working around a problem that will go away in 7.5. If you don't anticipate going to production for six months or so, you could adopt CVS tip as your development platform, with the expectation that 7.5 will be released by the time you need a production system. I wouldn't recommend running CVS tip as a production database but it should be plenty stable enough for devel purposes. Another plan would be to use int4 columns for the time being with the intention of widening them to int8 when you move to 7.5. This would depend on how soon you anticipate needing values > 32 bits, of course. regards, tom lane