Re: Undo logs

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Undo logs
Date: 2018-05-28 11:40:50
Message-ID: CANP8+jL=KGODyCnKqp5rceLJHkJ+Mksc0+qhjibKivLAnswwcA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24 May 2018 at 23:22, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> wrote:

> As announced elsewhere[1][2][3], at EnterpriseDB we are working on a
> proposal to add in-place updates with undo logs to PostgreSQL. The
> goal is to improve performance and resource usage by recycling space
> better.

Cool

> The lowest level piece of this work is a physical undo log manager,

> 1. Efficient appending of new undo data from many concurrent
> backends. Like logs.
> 2. Efficient discarding of old undo data that isn't needed anymore.
> Like queues.
> 3. Efficient buffered random reading of undo data. Like relations.

Like an SLRU?

> [4] https://github.com/EnterpriseDB/zheap/tree/undo-log-storage/src/backend/access/undo
> [5] https://github.com/EnterpriseDB/zheap/tree/undo-log-storage/src/backend/storage/smgr

I think there are quite a few design decisions there that need to be
discussed, so lets crack on and discuss them please.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

  • Undo logs at 2018-05-24 22:22:11 from Thomas Munro

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vladimir Sitnikov 2018-05-28 14:19:25 Re: [JDBC] [HACKERS] PGSERVICEFILE as a connection string parameter
Previous Message Yuriy Zhuravlev 2018-05-28 10:00:03 Re: Is a modern build system acceptable for older platforms