Re: WIP: Avoid creation of the free space map for small tables

From: John Naylor <jcnaylor(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: Avoid creation of the free space map for small tables
Date: 2019-01-07 20:56:59
Message-ID: CAJVSVGXLtaB_u717e+C8Jq5T5VSo=vJ_Zfmy8PKn=35PFz-ztA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On 1/3/19, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Yeah, that makes sense, John, can you provide a patch on top of the
> current patch where we check either the last block or every other
> block.

I've attached two patches for testing. Each one applies on top of the
current patch.

Mithun, I'll respond to your other review comments later this week.

-John Naylor

Attachment Content-Type Size
fsm-last-page-only.patch text/x-patch 855 bytes
fsm-every-other-page.patch text/x-patch 2.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2019-01-07 21:00:14 Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)
Previous Message Justin Pryzby 2019-01-07 19:34:08 Re: ALTER INDEX fails on partitioned index