X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AEE465E37D0 for ; Thu, 12 Aug 2004 14:09:15 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 50947-10 for ; Thu, 12 Aug 2004 17:09:05 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 49C525E37CB for ; Thu, 12 Aug 2004 14:09:06 -0300 (ADT) 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 i7CH929v000120; Thu, 12 Aug 2004 13:09:02 -0400 (EDT) To: "Merlin Moncure" Cc: pgsql-performance@postgresql.org, "Jason Coene" Subject: Re: Hardware upgrade for a high-traffic database In-reply-to: <6EE64EF3AB31D5448D0007DD34EEB3412A7450@Herge.rcsinc.local> References: <6EE64EF3AB31D5448D0007DD34EEB3412A7450@Herge.rcsinc.local> Comments: In-reply-to "Merlin Moncure" message dated "Thu, 12 Aug 2004 12:58:10 -0400" Date: Thu, 12 Aug 2004 13:09:02 -0400 Message-ID: <119.1092330542@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/189 X-Sequence-Number: 7825 "Merlin Moncure" writes: > The following suggestion works in two principles: one is that instead of > using timestamps for ordering, integers are quicker, The difference would be pretty marginal --- especially if you choose to use bigints instead of ints. (A timestamp is just a float8 or bigint under the hood, and is no more expensive to compare than those datatypes. Timestamps *are* expensive to convert for I/O, but comparison does not have to do that.) I wouldn't recommend kluging up your data schema just for that. regards, tom lane