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

From: John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(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-02-23 08:01:11
Message-ID: CACPNZCs9K0Kre+_iCY+WJQmBq69f0Bo-7qScC7r7uy_cKWEdpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 22, 2019 at 3:59 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> The reason for not pushing much on making the test pass for
> nonstandard block sizes is that when I tried existing tests, there
> were already some failures.

FWIW, I currently see 8 failures (attached).

--
John Naylor https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
jcn-16blk-regress.diffs application/octet-stream 31.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2019-02-23 08:13:21 Re: Why don't we have a small reserved OID range for patch revisions?
Previous Message John Naylor 2019-02-23 07:54:18 Re: WIP: Avoid creation of the free space map for small tables