| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Willis, Ian (Ento, Canberra)'" <Ian(dot)Willis(at)ento(dot)csiro(dot)au>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | RE: Best practice |
| Date: | 2001-04-20 22:11:29 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D33C2@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> What would the the best choice for the WAL mirroring, raid3
> or 5. How big does the WAL grow? mirroring is fine as long
> as the size isn't too big.
1. For each transaction that made some updates to DB
all log records must be available.
2. Server removes "old" (see 1.) 16Mb log files only at
checkpoint time (each ~300 sec by default).
So, in the system with low update rate/short update TX
there will be only 1 - 2 16Mb log files at any time.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Travis Bauer | 2001-04-20 22:14:03 | Re: Trusted plperl |
| Previous Message | Joel Burton | 2001-04-20 21:33:13 | Re: Trusted plperl |