Building a DB with performance in mind

From: Alexander Ranaldi <alexranaldi(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Building a DB with performance in mind
Date: 2005-03-17 15:56:10
Message-ID: c7c05762050317075614cc0bfe@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Greetings everyone,

I am about to migrate to Postgres from MySQL. My DB isn't enormous (<
1gb), consists mostly of just text, but is accessed quite heavily.
Because size isn't a huge issue, but performance is, I am willing to
normalize as necessary.

Currently I have a table "Entries" containing 500k rows. The table
contains many text columns, and a few others:
EntryID (unique, indexed)
UserID (references "Users" table, indexed)
Private (boolean. indexed)

Most of my queries return rows based on UserID, and also only if
Private is FALSE. Would it be in the interest of best performance to
split this table into two tables: "EntriesPrivate",
"EntriesNotPrivate" and remove the "Private" column?

I appreciate any feedback. I'm certainly not a DB design expert. :)

Thanks,
Alex

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Steinar H. Gunderson 2005-03-17 16:09:34 Re: Building a DB with performance in mind
Previous Message Lending, Rune 2005-03-17 14:01:43 queries on huge tables