| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is VACUUM still crash-safe? |
| Date: | 2000-12-11 17:36:55 |
| Message-ID: | 7726.976556215@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> writes:
> If we move tuples in already committed state, a page with new
> tuple position goes to disk and backend crashes before page with
> old tuple position updated then we'll have two version of tuple
> after restart (new tuple with HEAP_MOVED_IN is valid and there is
> no HEAP_MOVED_OFF in old tuple version).
That's not good. Perhaps VACUUM still needs to fsync the file before
its internal commit?
> I don't know how bad is it for TOAST tables though.
I still don't see anything here that affects the handling of TOAST
tables, which was Hiroshi's original complaint.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Guenter | 2000-12-11 17:54:18 | Re: Re: CRC |
| Previous Message | Mikheev, Vadim | 2000-12-11 17:20:41 | RE: suggest remove of elog in xlog.c |