| From: | "Rod Taylor" <rbt(at)barchord(dot)com> |
|---|---|
| To: | "John Moore" <nj7e(at)yahoo(dot)com> |
| Cc: | "Hackers List" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: Backup and Recovery |
| Date: | 2001-07-03 19:40:56 |
| Message-ID: | 000b01c103f8$14634f70$2205010a@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> With stock PostgreSQL... how many committed transactions can one
lose
> on a simple system crash/reboot? With Oracle or Informix, the answer
> is zero. Is that true with PostgreSQL in fsync mode? If not, does it
> lose all in the log, or just those not yet written to the DB?
With WAL the theory is that it will not lose a committed transaction.
Bugs have plagged previous versions (7.1.2 looks clean) and it none
(Oracle, Informix, Postgres) can protect against coding errors in the
certain cases but from general power failure it's fine.
This assumes adequate hardware too. Some harddrives claim to have
written when they haven't among other things, but Postgres itself
won't lose the information -- your hardware might :do that silently
though.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-07-03 19:45:59 | Re: [PATCH] Patch to make pg_hba.conf handle virtualhost access control and samehost keyword |
| Previous Message | Nathan Myers | 2001-07-03 19:36:19 | Re: Buffer access rules, and a probable bug |