From: | tom <tom(at)tacocat(dot)net> |
---|---|
To: | Don Lavelle <don(dot)lavelle(dot)bulk(at)gmail(dot)com> |
Cc: | Postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Beginner's Questions |
Date: | 2007-03-09 12:11:52 |
Message-ID: | A8B32CA3-4426-4C35-9151-860951CB20EE@tacocat.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm running my database on a Pentium 2 with 450MHz CPU.
It runs dbmail and spamassassin's Bayes and has overhead available.
You'll find it works well enough for your database size.
As for being it overkill. I think you've answered your own questions:
I don't have to write as much code -- less bugs, less development time.
It's know to be reliable for what I'm doing -- less bugs, less
testing time.
So, if it *can* run on your machine why wouldn't you run it on your
machine?
I don't limit this thinking to just postgresql... You've identified
postgresql as something that can provide you with a simpler solution
to the architecture, you have sufficient hardware for it. And if for
some reason your estimates are wrong about the size of the project
you can easily grow for sometime with minor modifications, if any, to
your application.
On Mar 9, 2007, at 7:03 AM, Don Lavelle wrote:
> Hey, All,
>
> I'm working on a project (for a friend and for self-education) and
> want to learn a little more about what sorts of applications
> PostgreSQL is used for. I'm currently looking at a single-computer
> desktop application that may be scaled to a client-server model
> with multiple desktop clients and a centralized server.
>
> My database is quite small (only 13 lucky tables, though that may
> expand a little) and will not hold a great amount of data. (There
> will be at most records in the thousands for the single-user or
> tens of thousands for the multi-user.) I will either use Java or C+
> + for the project. I would run PostgreSQL as a child process.
>
> Is PostgreSQL overkill for such a project? My other choices are to
> go with a flat-file format or to use an embedded SQL server. The
> reason to go with PostgreSQL are that I don't have to write as much
> code, it's known to be reliable for what I'm doing, and it's known
> to be reliable for what I might be doing. The reason to not go
> with PostgreSQL is that it might be too much for a modest personal
> computer; I don't know that the computers running this will even
> have XP. (I'm not a MS Windows user, myself, unless I have to be.
> My development boxes are a 1.1 GHz Athlon with 512 RAM with XP and
> a dual-processor G4 with MacOS 10.4.)
>
> Are there ballpark requirements for what such a database will need
> to run?
>
> Thanks!
>
> Don
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org/
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jorge Godoy | 2007-03-09 12:34:03 | Re: Beginner's Questions |
Previous Message | Don Lavelle | 2007-03-09 12:03:12 | Beginner's Questions |