AW: Plans for solving the VACUUM problem

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Barry Lind'" <barry(at)xythos(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: Plans for solving the VACUUM problem
Date: 2001-05-22 08:16:10
Message-ID: 11C1E6749A55D411A9670001FA6879633682E8@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> REDO in oracle is done by something known as a 'rollback segment'.

You are not seriously saying that you like the "rollback segments" in Oracle.
They only cause trouble:
1. configuration (for every different workload you need a different config)
2. snapshot too old
3. tx abort because rollback segments are full
4. They use up huge amounts of space (e.g. 20 Gb rollback seg for a 120 Gb SAP)

If I read the papers correctly Version 9 gets rid of Point 1 but the rest ...

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2001-05-22 08:20:26 XMAX weirdness (was: Plans for solving the VACUUM problem)
Previous Message Zeugswetter Andreas SB 2001-05-22 08:06:54 AW: AW: Plans for solving the VACUUM problem