Marc SCHAEFER writes:
> - log all transactions to a special log file, that can be used for
> backup purposes:
Will be in 7.1.
> - hard transactions: cutting the power to a PostgreSQL server
> may cause data loss and/or data corruption. Some databases use
> sophisticated techniques to ensure serialization of operation
> through journaling, redoing some of the transactions at
> bootup time if required.
This is really the same as above in implementation. So same answer.
> - the ability to synchronize two database servers, with only the
> changes being exchanged, live. Or the ability to have many
> servers in a load-balancing or data scattering pool.
Something like this has recently been announced as add-on from PostgreSQL,
Inc. (www.pgsql.com) Haven't seen it used, though.
> - ability to have databases bigger than the host's maximum file size
That has been available for quite a while.
--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
