pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bill Moran <wmoran@potentialtech.com>
To: Jeff <threshar@torgo.978.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Fixed width rows faster?
Date: Fri, 05 Mar 2004 09:07:34 -0500
Message-ID: <404889A6.7@potentialtech.com> (raw)
In-Reply-To: <E9C9F3C2-6EA9-11D8-A89E-000D9366F0C4@torgo.978.org>
References: <E9C9F3C2-6EA9-11D8-A89E-000D9366F0C4@torgo.978.org>

Jeff wrote:
> I'm guessing the answer to this is "no"
> 
> Is there any performance advantage to using a fixed width row (with PG)?

No.  The user docs state that the performance is equal for char, varchar
and text.

> I've heard this theory a few times and I think it is based on older, 
> different databases

MySQL used to have this issue (I don't know if it still does or not) to
the point that the docs once claimed that an index on a varchar was barely
as fast as a char with no index at all.

> and we have also some custom software here that uses 
> fixed width rows to be able to hit row N in O(1), but that isn't what 
> I'd call a real database.

Isn't needed in modern versions of Postgres, but I don't know (historically)
if it ever was or not.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com




view thread (23+ messages)  latest in thread

Message-ID: <404889A6.7@potentialtech.com>
Permalink:  ../404889A6.7@potentialtech.com/
Also on:    postgresql.org/message-id/404889A6.7@potentialtech.com

 · 

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: wmoran@potentialtech.com, threshar@torgo.978.org
  Subject: Re: Fixed width rows faster?
  In-Reply-To: <404889A6.7@potentialtech.com>

* 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