Re: zheap: a new storage format for PostgreSQL - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: zheap: a new storage format for PostgreSQL
Date
Msg-id CAA4eK1+Lop8aXu7zNXWTQKxhZBnnAabLS9S1S+LY_XNAp5oJ6A@mail.gmail.com
Whole thread Raw
In response to Re: zheap: a new storage format for PostgreSQL  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: zheap: a new storage format for PostgreSQL  (Mithun Cy <mithun.cy@enterprisedb.com>)
List pgsql-hackers
On Thu, Dec 6, 2018 at 10:03 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:
>
> čt 6. 12. 2018 v 5:02 odesílatel Mithun Cy <mithun.cy@enterprisedb.com> napsal:
>>
>> COPY command seems to have improved very slightly with zheap in both with size of wal and execution time. I also did
sometests with insert statement where I could see some regression in zheap when compared to heap with respect to
executiontime. With further more investigation I will reply here. 
>>
>
> 20% of size reduction looks like effect of fill factor.
>

I think it is because of smaller zheap tuple sizes.  Mithun can tell
more about setup whether he has used different fillfactor or anything
else which could lead to such a big difference.

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


pgsql-hackers by date:

Previous
From: "Nagaura, Ryohei"
Date:
Subject: RE: Timeout parameters
Next
From: Michael Paquier
Date:
Subject: Re: Use durable_unlink for .ready and .done files for WAL segmentremoval