Re: TOAST performance (was Re: [GENERAL] Delete Perform

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Brian Beuning'" <bbeuning(at)mindspring(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: TOAST performance (was Re: [GENERAL] Delete Perform
Date: 2001-12-21 00:03:58
Message-ID: 3705826352029646A3E91C53F7189E32518459@sectorbase2.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> If "pre-page WAL write" means the value of the page before the current
> changes, then there is generally another reason for writing it out.

Bruce, "*pre*-page" is confusing - we write "after-change" page
image to WAL.

> When the system comes back up, we need to do a rollback on
> transaction B since it did not commit and we need the "pre-page"
> to know how to undo the change for B that got saved in step 6 above.

Brian, PGSQL still uses non-overwriting storage manager -
removing rows inserted by aborted transactions is not required.

Vadim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message mlw 2001-12-21 00:53:10 Integer aggregate and enum
Previous Message Brian Beuning 2001-12-20 23:33:49 Re: TOAST performance (was Re: [GENERAL] Delete Performance)