| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Marc SCHAEFER <schaefer(at)alphanet(dot)ch> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Some advanced database features, are they present in PostgreSQL |
| Date: | 2000-10-10 17:08:14 |
| Message-ID: | Pine.LNX.4.21.0010101905160.759-100000@peter.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-10-10 17:09:24 | Re: [HACKERS] My new job |
| Previous Message | Tom Lane | 2000-10-10 17:02:52 | Re: [HACKERS] My new job |