agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

From: postgres@webcom.com
To: postgres@postgres.Berkeley.EDU
Cc: leavitt@webcom.com
Subject: suitable for mission critical?
Date: Fri, 19 Aug 94 18:40:22 PDT
Message-ID: <199408200152.SAA18063@nobozo.CS.Berkeley.EDU> (raw)

Dear postgres users, gods, and godesses:

We're starting a small online-service on the Internet, with an HP-UX box
as our main server.  We need a robust transaction engine to manage
our accounts, etc.

The commercial products that either run on the HP box or have client
APIs for HP-UX that allow us to use them from the HP are way out of
our budget.

Our first consideration is reliability.  Performance is not a major 
issue right now (although hopefully later it will be :) ).  Another
major plus for us is a perl interface.  

Given our budget constraints, and our low throughput requirements,
and the perl interface, and the cool POSTWUEL language, Postgres
looks very attractive.  Our major concern about using it is reliability.

We can live with having to export, rebuild, and import a table once
in a while.  We don't want to be fighting fires constatnly though, of
course.

The question I'm leading up to is:  what are peoples' opinions
on the prudence of using Postres to run a small business?  I know
it's not something you'd want to use to run a Fortune 500 accounting
application, but is it acceptable for something in the range of
50-200 invoices a month?  Or would you strongly advise against
running our business on it?

The database should stay under 100MB over it's lifetime.

That's our main question.  This next question is more just
curiosity.  I don't care if nobody wants to take the time
to answer this one.  I'll RTFM.  :)

Question #2:

I haven't yet figured out just how OO Postgres really is.

I'm new to OO, so I can't pose formal questions, but can I 
do stuff like this with postgres:

(pseudo quel)

customer.email("Your payment is late")
where customer.days_past_due > 30

customer.suspend where customer.days_past_due > 60

invoice.paid(fetch recvd.check.against_invoice
where received.check.date = today)

customer.set_status(":)") where customer.paid_up = TRUE

In other words, can I define methods on objects that accept
parms and operate on the instance object, or a set of
instances defined by an ad hoc set qualifer?  And can these
methods be inherited?  And can those methods be complex
transactions?  And can the methods be inherited?  

Okay, now I'll go see if I can figure out how to print that
postscript manual.  

Thanks for your advice!

Chris
Web Communications


==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================

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 using the --to and --cc options:
  reply via email

  To: postgres@postgres.berkeley.edu
  Cc: postgres@webcom.com, leavitt@webcom.com
  Subject: Re: suitable for mission critical?
  In-Reply-To: <199408200152.SAA18063@nobozo.CS.Berkeley.EDU>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox