| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: Plans for solving the VACUUM problem |
| Date: | 2001-05-23 09:25:12 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633682F0@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >If community will not like UNDO then I'll probably try to implement
> >dead space collector which will read log files and so on.
>
> I'd vote for UNDO; in terms of usability & friendliness it's a big win.
Could you please try it a little more verbose ? I am very interested in
the advantages you see in "UNDO for rollback only".
pg_log is a very big argument, but couldn't we try to change the format
to something that only stores ranges of aborted txn's in a btree like format ?
Now that we have WAL, that should be possible.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2001-05-23 10:11:49 | Re: Plans for solving the VACUUM problem |
| Previous Message | Philip Warner | 2001-05-23 08:58:58 | RE: Plans for solving the VACUUM problem |