Quote:>Perhaps, you could be the test site for postgres in a real-life
>business system. I'm thinking that if you chose a commercial DBMS
>such as those above, that whatever data is being written to them,
>is simultaneously being written to the free Postgres SQL or MYsql.
And really what this represents is a situation of decoupling the
application from the DBMS, probably by putting some form of middleware
in between your application and the DB.
Note that this sort of thing can be a wise move even if you're using a
"really a whole lot more robust" DB; the basic idea to make the use of
PostgreSQL supportable in a "high reliance" application is to add in
some transaction logging so that if the system falls down, you can go
back to the last full backup and apply all the changes that were
recorded in the transaction log. (Oracle calls this sort of thing
"archive logs.")
The wisdom comes in when you log the transactions at the "higher level
logical transaction" level; this allows a more intelligent recovery
than you get out of something like Oracle's "archive logs," which just
plain record everything that happens, relevant to processing or not.
At any rate, the use of middleware in this manner can increase the
reliability of the system even if the database is somewhat fragile.
And it looks like a major new release of PostgreSQL is coming quite
soon; we'll see what that offers...
--
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer <http://www.hex.net/~cbbrowne/lsf.html>
by