| From: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ian Harding <iharding(at)pakrat(dot)com>, Martijn van Oosterhout <kleptog(at)cupid(dot)suninternet(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Re: Loading optimization |
| Date: | 2001-01-11 22:38:44 |
| Message-ID: | 20010111143844.K7240@fw.wintelcom.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
* Mikheev, Vadim <vmikheev(at)SECTORBASE(dot)COM> [010111 14:14] wrote:
> > We have talked about this, but we have not seen enought
> > corruption cases to warrant it.
>
> Huh?! Just pg_ctl -m immediate stop in <= 7.0.X with high
> insert activity and ... pray.
no kidding. :)
>
> It's changed in 7.1 by WAL - btree doesn't lose tuples in split
> ops anymore and in after crash restart you'll never see btree
> tuples pointing to unexisted heap tuples (because of index tuples
> inserted/logged after heap ones).
The main thing is that I consider myself to be pretty ok with
postgresql right now, but it's still a major amount of manual
labor to _absolutely_ make sure no data has been lost and make
sure that no more corruption exists that could get the server
to die or go off into some inifinite loop. We really haven't
had these problems for a long time but it's be really comforting
to have something that pretty much made sure it wouldn't.
--
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]
"I have the heart of a child; I keep it in a jar on my desk."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikheev, Vadim | 2001-01-11 22:51:09 | RE: Re: Loading optimization |
| Previous Message | Wade D. Oberpriller | 2001-01-11 22:28:40 | initdb on build machine and moving to production machine |