Re: PostgreSQL MVCC and alternative REDO implementation - my thoughts

From: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL MVCC and alternative REDO implementation - my thoughts
Date: 2018-11-18 13:20:04
Message-ID: 8358c44f-ee76-d4f6-3956-ed67898cc0c0@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On 18/11/18 2:04 μ.μ., Gerhard Wiesinger wrote:
> On 18.11.2018 12:14, Martín Marqués wrote:
>> El 18/11/18 a las 04:49, Gerhard Wiesinger escribió:
>>> Hello,
>>>
>>> I just read that blog article and I think switching to REDO logic is
>>> not
>>> a good idea.
>> I think you got it the other way around. Postgres implementes REDO, that
>> is, move forward by REDOing the changes which are stored in WAL files
>>
>> BTW, could you point us to the blog you read this?
>>
>> Maybe you got REDO and UNDO mixed up.
>
>
> Yes, I ment UNDO ...
>
> Link is here:
>
> https://severalnines.com/blog/five-cool-things-i-learned-postgresql-conference-europe-2018
>
>
> sunday morning, too early :-)

In this blog I had the role of the reporter for the event :)

When and if this makes it to the core, both heaps will be supported.
Nevertheless this sounds exciting feature to have, however lots of work
must be done before PostgreSQL is able to adopt this in an elegant manner.

>
> Ciao,
>
> Gerhard
>
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Yuri Kanivetsky 2018-11-18 21:50:38 New timeline when starting with a restored data dir
Previous Message Gerhard Wiesinger 2018-11-18 12:04:37 Re: PostgreSQL MVCC and alternative REDO implementation - my thoughts