RE: Plans for solving the VACUUM problem

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Hannu Krosing'" <hannu(at)tm(dot)ee>
Cc: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'Don Baccus'" <dhogaza(at)pacifier(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: RE: Plans for solving the VACUUM problem
Date: 2001-05-29 20:37:03
Message-ID: 3705826352029646A3E91C53F7189E32016660@sectorbase2.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > > OTOH it is possible to do without rolling back at all as
> > > MySQL folks have shown us ;)
> >
> > Not with SDB tables which support transactions.
>
> My point was that MySQL was used quite a long time without it
> and still quite many useful applications were produced.

And my point was that needless to talk about rollbacks in
non-transaction system and in transaction system one has to
implement rollback somehow.

> BTW, do you know what strategy is used by BSDDB/SDB for
> rollback/undo ?

AFAIR, they use O-smgr => UNDO is required.

Vadim

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-05-29 21:03:36 Re: pg_log ??
Previous Message Nathan Myers 2001-05-29 20:03:35 Re: Re: charin(), text_char() should return something else for empty input