From: Edipo Elder Fernandes de Melo <edipoelder@ig.com.br>
To: pgsql-sql@postgresql.org
Subject: Large or Small tables?
Date: Mon, 15 Apr 2002 14:38:05 -0300
Message-ID: <20020415173808.1190E4776F5@postgresql.org> (raw)
Hi all,
I'm developing a selective system for selection of students for a
university. My system has tables for candidate, score, answers, exams, and
others.
The candidate table has about 40 columns, of that, 35 are candidate
information (name, address, etc), 10 are for score, status, etc, and use 2
columns as primary key (a idCandidate and idSelection).
The answers table has five columns: idSelection, idExam, idQuestion,
idCandidate, and answer. Better explained: for each answer, it has a record
(it's a lot of tuples - about 25000 candidates x 8 exams x 15 questions for
exams = 3 milions!)
The score table has idCandidate, idSelection, idExam, and score of each
candidate and exam.
Basicaly, to process the selection, I count how much questions the
candidate got correct, make some calc, and find a score.
My question is if is better have a unique candidate table with all
information of a candidate, or broke the table in two tables (one to
candidate information, and the other for score and status) for process of
find score. Or better, Having a large table in a middle of a process, where
i use only 10% of information on it, slow it down?
Thanks for all,
Edipo Elder
[edipoelder@ig.com.br]
_________________________________________________________________________
Você podia estar baixando sua musica predileta, enquanto lia esse e-mail.
Não perca tempo, tenha acesso rápido a internet com o Super iG.
http://registro.ig.com.br/superig
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-sql@postgresql.org
Cc: edipoelder@ig.com.br
Subject: Re: Large or Small tables?
In-Reply-To: <20020415173808.1190E4776F5@postgresql.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