| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Alfred Perlstein'" <bright(at)wintelcom(dot)net> |
| 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:51:09 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D3265@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > 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.
Just remembered from my prev observations in index area that
it's still possible to get infinite loop if root page was
splitted but new root was not created...
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2001-01-11 22:54:46 | Re: PostgreSQL v7.1BETA3 Bundled and Available ... |
| Previous Message | Alfred Perlstein | 2001-01-11 22:38:44 | Re: Re: Loading optimization |