| From: | Michael Devogelaere <michael(at)digibel(dot)be> |
|---|---|
| To: | Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | Jan Wieck <janwieck(at)yahoo(dot)com>, Michael Devogelaere <michael(at)digibel(dot)be>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL crashes with Qmail-SQL |
| Date: | 2002-01-24 16:59:43 |
| Message-ID: | 20020124175943.A6664@digibel.be |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 25, 2002 at 03:48:40AM +1100, Justin Clift wrote:
> Jan Wieck wrote:
> >
> <snip>
> >
> > As said, "simple read-only" is not really something you want
> > a full featured RDBMS for. Maybe you are better off with a
> > simple and stupid system on the feature level of gdbm or
> > MySql.
> >
> > Jan
>
> I'd agree with this on the query-level functionality... but...
>
> Michael, does Qmail-SQL *store* the email in the database? (haven't
> checked)
No way ;) Only the user/authentication-management moved to the database.
>
> If so, there's no way I'd want new customer inquiries or other
> *important* email stored in a system which didn't know how to fully
> recover if the server crashes.
Neither do i. But i know there exists a patch (qmail seems to consist merely
of patches) which stores the mail in a database. Maybe you can use this to
"save" helpdesk-calls ;)
Regards,
Michael.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitch Vincent | 2002-01-24 17:22:34 | Re: PostgreSQL crashes with Qmail-SQL |
| Previous Message | Ross J. Reedstrom | 2002-01-24 16:58:14 | Re: Add OR REPLACE clauses to non-FUNCTION object creation in PostgreSQL 7.3 |