X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8FD0CD1D1CD for ; Wed, 11 Feb 2004 23:24:43 +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 58539-02 for ; Wed, 11 Feb 2004 19:24:41 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id D208BD1D1C3 for ; Wed, 11 Feb 2004 19:24:39 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1BNOfGp024097; Wed, 11 Feb 2004 18:24:41 -0500 (EST) To: Mark Harrison Cc: pgsql-performance@postgresql.org Subject: Re: coercing int to bigint for indexing purposes In-reply-to: <402AAEF1.2050703@pixar.com> References: <402AAEF1.2050703@pixar.com> Comments: In-reply-to Mark Harrison message dated "Wed, 11 Feb 2004 14:38:41 -0800" Date: Wed, 11 Feb 2004 18:24:41 -0500 Message-ID: <24096.1076541881@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/142 X-Sequence-Number: 5666 Mark Harrison writes: > Is there a way to automatically coerce an int into a bigint for > indexing purposes? This problem is fixed in CVS tip. regards, tom lane