pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: pgsql-performance@postgresql.org, "Jason Coene" <jcoene@gotfrag.com>
Subject: Re: Hardware upgrade for a high-traffic database
Date: Thu, 12 Aug 2004 13:09:02 -0400
Message-ID: <119.1092330542@sss.pgh.pa.us> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A7450@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A7450@Herge.rcsinc.local>

"Merlin Moncure" <merlin.moncure@rcsonline.com> 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



view thread (29+ messages)  latest in thread

Message-ID: <119.1092330542@sss.pgh.pa.us>
Permalink:  ../119.1092330542@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/119.1092330542@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, merlin.moncure@rcsonline.com, jcoene@gotfrag.com
  Subject: Re: Hardware upgrade for a high-traffic database
  In-Reply-To: <119.1092330542@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox