Re: zheap: a new storage format for PostgreSQL

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Satyanarayana Narlapuram <Satyanarayana(dot)Narlapuram(at)microsoft(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: zheap: a new storage format for PostgreSQL
Date: 2018-03-01 17:08:44
Message-ID: CAA4eK1+pk8Brpnb=WHr1eLnYW-Pfb623pkUQUh6Vze2SBH0HTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 1, 2018 at 9:00 PM, Satyanarayana Narlapuram
<Satyanarayana(dot)Narlapuram(at)microsoft(dot)com> wrote:
>
>>> Cons
>
>>> -----------
>>> 1. Deletes can be somewhat expensive.
>>> 2. Transaction aborts will be expensive.
>>> 3. Updates that update most of the indexed columns can be somewhat
>>> expensive.
>
> Given transaction aborts are expensive, is there any impact on the crash
> recovery?

I don't think there should be any direct impact of aborts on recovery
time as we start processing the undo records after recovery is done.
Basically, we invoke undo worker after recovery which performs the
aborts in the background.

>Did you perform any tests on the recovery duration?
>

Not yet, but I think we will do it after making some more progress.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2018-03-01 17:13:18 Re: 2018-03 Commitfest starts tomorrow
Previous Message David Steele 2018-03-01 17:05:41 Re: 2018-03 Commitfest starts tomorrow