pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew Hixson <hixson@frozenwave.com>
To: pgsql-sql@postgresql.org
Subject: 2 million+ entries
Date: Fri, 20 Aug 1999 16:59:51 -0700
Message-ID: <99082017435704.17950@kashmir> (raw)

Hi,
  I'm going to be working on a project soon that involves an SQL database.  If
I have my way it will be using PostgreSQL 6.5 on a dual PII-350 with 256 MB of
RAM and two 18GB UW2 SCSI drives (Seagate Barracudas).  However there is a
possibility that it could be running on an NT server with even beefier hardware.
  What I'm wondering is; is there any problem with Postgres handling a table
with 2 million entries in it?  Is there an NT solution that would work better? 
Personally I can't stand NT, but its not really my decision to make.  This is
going to be mission critical so must remain rock solid 24x7.  (On second
thought that kindof rules out NT doesn't it...? :)
  Anyway here is the table structure that my project manager came up with.  I
mentioned that it might be better to put the "Subscriber Table", "Usage Table",
"Personal Information Table", "Credit Card Information Table", and "Interests
Table" all into one larger table.  So now we're wondering:  Does having
separate tables like this make sense for speeding up lookups or would it be
faster with my one large table idea?  In either case will PostgreSQL be able to
handle this much data gracefully?
  Thanks in advance for any insight into this.
   -M@



Subscriber Table
	UserName (unique)
	Password
	Active

Usage Table
	UserName (unique)
	DiskSpaceAuthorizedAmount
	DiskSpaceAuthorizedDate
	LastLogin
	FailedAttempts
	DefaultDirectoryLocal
	DefaultDirectoryzDisk
	AccountCreateDate
	OverDrawn
	WarningFlag
	NotifyFlag

Personal Information Table
	UserName (unique)
	FirstName
	LastName
	EmailAddress
	HomeAddress1
	HomeAddress2
	HomeCity
	HomeState
	HomeCountry
	HomePostalCode
	HomePhone1
	HomePhone2
	HomeFax
	WorkAddress1
	WorkAddress2
	WorkCity
	WorkState
	WorkCountry
	WorkPostalCode
	WorkPhone1
	WorkPhone2
	WorkFax
	Sex
	BirthYear
	Interests

Credit Card Info Table
	UserName (unique)
	CreditCard
	CardNumber
	IssuingBank
	NameOnCard
	ExpirationDate
	BillingName
	BillingAddress1
	BillingAddress2
	BillingCity
	BillingState
	BillingPostalCode

Disk Space Pricing Table
	InitialFreeSize
	NextBlockSize
	NextBlockPrice
	QuantityDiscount

Interests Table
	Sports - Active”
	Sports - Leisure”
	Theater”
	Collecting”
	Fashion”
--
Matthew Hixson - CIO 
FroZenWave Communications 
http://www.frozenwave.com



view thread (12+ messages)  latest in thread

Message-ID: <99082017435704.17950@kashmir>
Permalink:  ../99082017435704.17950@kashmir/
Also on:    postgresql.org/message-id/99082017435704.17950@kashmir

 · 

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 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-sql@postgresql.org
  Cc: hixson@frozenwave.com
  Subject: Re: 2 million+ entries
  In-Reply-To: <99082017435704.17950@kashmir>
  References: <99082017435704.17950@kashmir>

* 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