From: Jim C. Nasby <jim@nasby.net>
To: pgsql-performance@postgresql.org
Subject: Re: sequential scans on few columns tables
Date: Mon, 16 Jun 2003 17:45:27 -0500
Message-ID: <20030616224527.GM40542@flake.decibel.org> (raw)
In-Reply-To: <3EEE1F54.3030507@klaster.net>
References: <3EEE1F54.3030507@klaster.net>
On Mon, Jun 16, 2003 at 09:49:40PM +0200, Tomasz Myrta wrote:
> by denormalizing tables. Let's say we have table "users" which we split
> into 1:1 relation "users_header" and "users_data". We put searchable
> columns into users_header and rest of them into users_data. users_data
> have some integer foreign key referencing to users_header.
>
> What do you think about it? Does the Postgres use advantages of small
> table users_header? Sequential scan on memory cached table should speed
> up queries, the rest columns are in integer-indexed table which
> shouldn't slow it down.
Keep in mind that pgsql has a pretty heafty per-row overhead of 23
bytes. If your data table has a bunch of big varchars then it might be
worth it, otherwise it might not be.
--
Jim C. Nasby (aka Decibel!) jim@nasby.net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: jim@nasby.net
Subject: Re: sequential scans on few columns tables
In-Reply-To: <20030616224527.GM40542@flake.decibel.org>
References: <3EEE1F54.3030507@klaster.net> <20030616224527.GM40542@flake.decibel.org>
* 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