| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'nj7e(at)yahoo(dot)com'" <nj7e(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: Re: Backup and Recovery |
| Date: | 2001-07-03 19:55:47 |
| Message-ID: | 3705826352029646A3E91C53F7189E320166AA@sectorbase2.sectorbase.com |
| 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
It's true or better say should be, keeping in mind probability of bugs.
> lose all in the log, or just those not yet written to the DB?
BAR is not for "simple crash" but for the disk crashes. In this case
one will lose as much as WAL files lost.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Doug McNaught | 2001-07-03 20:01:30 | Re: funny (cache (?)) bug in postgres (7.x tested) |
| Previous Message | Tom Lane | 2001-07-03 19:45:59 | Re: [PATCH] Patch to make pg_hba.conf handle virtualhost access control and samehost keyword |